Subject: Re: [xsl] possible xalan error using function-available() and element-available() From: "James Fuller" <james.fuller.2007@xxxxxxxxx> Date: Thu, 4 Oct 2007 08:56:10 +0200 |
thank you both for the confirmation, this stylesheet must be from around 2002 so I wondered why they had worked before and what regression would have pushed Xalan to all of a sudden not work a few years later. I was surprised however by the amt of 'work' that the stylesheet was forcing the processor to go through, makes this an interesting test case. On 10/3/07, Abel Braaksma <abel.online@xxxxxxxxx> wrote: > Michael Kay wrote: > > I've always assumed that the only reason for testing function-available() > > was because you wanted to call the function, and since the function call has > > to use a static name, there's no conceivable reason to use > > function-available with a dynamic name. Perhaps I was wrong. > > > > > > > From the link I just send, I think more people tried it the way Jim > tried it, I quote from XALANJ-2223: > > "I wrote a stylesheet whose only purpose is to call "function-available" > on the EXSLT functions specified in an XML file. I first tested this in > Stylus Studio, using the Xalan 2.5.2 engine. When I run it, I get: > functionAvailable.xsl (19, 48): java.lang.RuntimeException: Unknown > error in XPath." > > > Perhaps this is the only niche where it makes sense to do it dynamically? I guess so. thx once again, Jim Fuller
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] possible xalan error usin, Abel Braaksma | Thread | Re: [xsl] possible xalan error usin, Abel Braaksma |
Re: [xsl] [XSL] id() in Ancestor No, G. Ken Holman | Date | Re: [xsl] [XSL] id() in Ancestor No, George Cristian Bina |
Month |