RE: [xsl] Linking Variable to the Path

["Yaswanth Kumar Ravella" <yaswanth.mtrx@xxxxxxxxx>]

Hi How about?
Java API for XML Processing (JAXP)
Will this work fine with JAXP?

Cheers
Yaswanth Ravella



-----Original Message-----
From: christoph.naber@xxxxxxxxxxxxxxxxxxx
[mailto:christoph.naber@xxxxxxxxxxxxxxxxxxx] 
Sent: Wednesday, August 22, 2007 5:18 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: RE: [xsl] Linking Variable to the Path

> I am getting Error :
> Description :
> Error during XSLT transformation: An unknown XPath extension function 
was
> called.
> 
> I am using Mozilla's Processor !

Sorry, Mozilla's XSLT-processor doesn't support EXSLT, as you can read in 
the blogpost below. I think there is no chance that you can achieve what 
you want with the Mozilla XSLT-processor. If you perform your 
transformations on client-side, you have to figure out another way, 
otherwise you may want to use saxon or another free available stylesheet 
processor that supports EXSLT.

http://dpcarlisle.blogspot.com/2007/05/exslt-node-set-function.html

Greetings Christoph


-----Original Message-----
From: David Carlisle [mailto:davidc@xxxxxxxxx] 
Sent: Wednesday, August 22, 2007 5:19 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [xsl] Linking Variable to the Path



> 	As you suggested I worked for a while to implement dyn:evaluate
> ...

> I am using Mozilla's Processor !

mozilla doesn't support extension functions (except they finally added
exslt:node-set in the test releases of firefox 3)
-----Original Message-----
From: Abel Braaksma [mailto:abel.online@xxxxxxxxx] 
Sent: Wednesday, August 22, 2007 6:08 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [xsl] Linking Variable to the Path

David Carlisle wrote:

>> I am using Mozilla's Processor !
>>     
>
> mozilla doesn't support extension functions (except they finally added
> exslt:node-set in the test releases of firefox 3)
On their main developer page they also claim to implement the 
exslt:regex functionality 
(http://developer.mozilla.org/en/docs/Firefox_3_for_developers#XSLT.2FXPath)
. 
On the dev mailing list, they seem to have done a lot more already, but 
I wonder whether it will make the final build: 
http://osdir.com/ml/mozilla.devel.layout.xslt/2006-12/msg00007.html.

To the OP: when you want this behavior fixed, the best thing you can do 
is using a two-phase solution, where you put the XML you want to reparse 
outside the document. If the XML is a result of a transform, you should 
save it and do a new transform. If the XML is inside a variable that you 
can make a global parameter, you can give the XSLT processor a DOM 
object as parameter (works on IE and FF) which you can use as node-set. 
Yet another solution is to use your current page and an XML section in 
conjunction with the document() function (but that depends on how your 
architecture would allow that).

I assume that many other approaches are thinkable, but the easiest would 
be to wait until january when FF 3.0 comes out ;)

Cheers,
-- Abel Braaksma