Cart
[Home] [By Thread] [By Date] [Recent Entries]
On 28/05/2010 15:09, Nick Leaton wrote:
In reverse order, on the fn: - good point, I'll remove them. But as I say since it means you are not using the main control construct of the language, the program needs a lot more code (and is a lot less flexible, template application typically automaticaly recururses through element structure, whereas passing a message parameter you need to do it by hand 9and if the input isn't exactly as you expect it fails, as you've found)
value-of doesn't tell you what you need to know as it removes the structure <foo><bar>hello</bar></foo> and "hello" both have string value "hello" but if they were in $message they would need very different paths. <xsl:message select="$message"/> would reveal more but still won't show you the difference between an element trade and a document node with element trade as child. Try putting as="element(trade)" on xsl:param that you think should get trade elements (and similarly other xsl;param) David > It is output correctly, however, the value-of selections from $message/ give the value, or don't give the value depending on whether or not its the compound xsl or the single stage xsl
This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. ________________________________________________________________________
|
