xsl-list
[Top] [All Lists]

Re: [xsl] extension functions returning temporary trees

2009-12-16 12:40:28
"hey Altova leave the kids alone" :)

2009/12/16 Brian Newman <brian(_dot_)newman(_at_)nssplus(_dot_)com>:
       Date: Tue, 15 Dec 2009 21:10:34 -0000
       To: <xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com>
       From: "Michael Kay" <mike(_at_)saxonica(_dot_)com>
       Subject: RE: [xsl] extension functions returning temporary trees
       Message-ID: <1D5F068BD1FC442F8BC67668EA070D35(_at_)Sealion>

       The way extension functions work is entirely a matter for the 
processor, but I would be rather surprised if the call mechanism allowed you 
to   return a string containing lexical XML, and implicitly parsed that XML 
and turned it into a tree of nodes. That conversion needs to be done e   
explicitly by calling an XML parser, either from the C# before returning from 
the extension, or from the XSLT code after returning.

       Regards,

       Michael Kay
       http://www.saxonica.com/
       http://twitter.com/michaelhkay

Turns out that it's a known bug in the Altova engine with a pre-existing 
trouble ticket.
"29642 - extension function support for result tree fragments and node sets"
Extension functions can't return node-sets/temporary trees
I guess I can stop banging me head against the wall - the wall will certainly 
appreciate it.

--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: 
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--



--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--

<Prev in Thread] Current Thread [Next in Thread>