 |
 |
 |
hi all
thanks for your solutions, however, i was wondering what happens if it is
there are more than one parameter within the xpath expression? is there an
legant solution for it?
i.e.
<xsl:param name="param1" select="'*'"/>
<xsl:param name="param2" select="'*'"/>
...
<xsl:for-each select="elementName[childName/something1=$param1 and
$childName/something2=$param2]>
...
<xsl:for-each>
Furthermore, i was wondering how will you set the parameter if the
parameter consist of white spaces (e.g. parameter='this is my parameter'),
in xalan-C command line will ignore the 'is', 'my' and 'parameter' and
throws an XPathParserexception error. do i use normalize-space($param1)?
but it seem it doesn't work, please help.
finally, can i use the following parameter for a xsl:for-each statement
using
xalan:evaluate? (e.g. "a/c='hello world'") sorry about throw so many
questions at the same time
Many thanks
regards
Kit
_________________________________________________________________
¦b±zªº¦æ°Ê¸Ë¸m¤W¶Ç°e±µ¦¬ Hotmail ¶l¥ó¡A½Ð²¾¦Ü¡Ghttp://mobile.msn.com
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
 | 



|  |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
|  |
| |
 |
 |
 |