cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Royal <>
Subject Re: Xalan CVS / Extension Functions / XSLTC
Date Fri, 05 Apr 2002 18:23:53 GMT
On Friday 05 April 2002 06:07 am, Stefano Mazzocchi wrote:
> It seems there is a problem in *our* TrAX usage that doesn't call
> getSystemID() (or something like that, I didn't dive futher, this was
> Jacek reporting to me a while ago) so XSLTC doesn't have a way to 'name'
> the compiled class and therefore falls back on the standard name which
> creates collisions if more than one stylesheet is called.

Gotcha. All of our pipelines have multiple trax transformations, so that 
kinda kills my hopes of xsltc for now at least.

> > BUT the latest Xalan is *MUCH* faster in interpreted mode (3x for the
> > stylesheet i was trying to optimize)
> Wow.

Its a very specific case, setting selected="selected" for selectbox options. 
I was doing a string comparison for each item, ie:

<xsl:transform match="page:item">
  <xsl:param name="value"/>

  <option value="{@value}">
    <xsl:if test="$value = @value"><xsl:attribute 

Its probably a corner case, but for a page with 10-15 dropdowns it made a 
huge difference.

> I can report that from Xalan CVS last week I had XSLTC running with no
> problems using the 'role trick' that we discussed for the
> TrAXTransformer.
> When I have a little little time I'll try to work on some changes and
> commit the results.

Thats what I followed also. It sounds like the class-naming is the current 
hiccup for me though. Thanks.

peter royal ->

To unsubscribe, e-mail:
For additional commands, email:

View raw message