|
[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Problem with iterating through a sequence of integ
Hi,
A few questions: 1. Would it not be preferable to invert the choose as in <xsl:for-each select="( . . .)"> <xsl:choose> <xsl:when test=". instance of xs:anyAtomicType"> <xsl:value-of select="."/> </xsl:when> <xsl:otherwise> <xsl:apply-templates select="$foo,." /> </xsl:otherwise> </xsl:choose> </xsl:for-each> especially since node() will also return text nodes that should probably be atomized ? 2. Also, wouldn't castable as be preferable to instance of, in this case ? If so, might one want to separate strings, boolean, numbers and integers, as in ... <xsl:choose> <xsl:when test=". instance of xs:integer"> ... </when> <xsl:when test=". instance of number()"> ... </when> <xsl:when test=". instance of xs:boolean"> ... </when> <xsl:when test=". castable as xs:integer"> ... </when> <xsl:when test=". castable as number()"> ... </when> <xsl:when test=". castable as xs:boolean"> ... </when> <xsl:when test=". castable as xs:string"> ... </when> <xsl:otherwise><xsl:apply-templates select="$foo,." /></xsl:otherwise> </xsl:choose> ? 3. What would be the best way to do this ?
Thanks. Cheers, ac ... David Carlisle a C)crit : a safer way is to use a global param, this prevents a static type error (as the system can not know that you will not pass in a node) but if you never do pass in a value then teh run time behaviour is as you wish:
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Cast Your Vote
We need your help – Vote for DataDirect XML Products!
Winners and finalists announced at SOA World Conference in November. Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|







