Subject: Re: [xsl] extension functions returning temporary trees|
From: Vyacheslav Sedov <vyacheslav.sedov@xxxxxxxxx>
Date: Wed, 16 Dec 2009 20:40:04 +0300
"hey Altova leave the kids alone" :) 2009/12/16 Brian Newman <brian.newman@xxxxxxxxxxx>: > B B B B Date: Tue, 15 Dec 2009 21:10:34 -0000 > B B B B To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx> > B B B B From: "Michael Kay" <mike@xxxxxxxxxxxx> > B B B B Subject: RE: [xsl] extension functions returning temporary trees > B B B B Message-ID: <1D5F068BD1FC442F8BC67668EA070D35@Sealion> > > B B B B 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 B 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 B explicitly by calling an XML parser, either from the C# before returning from the extension, or from the XSLT code after returning. > > B B B B Regards, > > B B B B Michael Kay > B B B B http://www.saxonica.com/ > B B B B 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.