You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Peter Royal <pr...@managingpartners.com> on 2002/04/04 23:03:44 UTC
Xalan CVS / Extension Functions / XSLTC
I downloaded the 04-04 CVS snapshot of Xalan-J and tried the XSLTC support,
but gave me some error about finding a class Gomer... (that's not the exact
error, but i stopped after that)..
BUT the latest Xalan is *MUCH* faster in interpreted mode (3x for the
stylesheet i was trying to optimize), *BUT* the extension function we use in
xsp.xsl wasn't working correctly, I was just getting empty strings. I am thus
running a modified xsp.xsl which removes use of the extension (I know my XSP
sources will be fine w/o it).
But the question is, I know I'm playing with fire with the Xalan CVS
snapshot. Has anyone had any luck with the recent ones wrt XSLTC or the
extension functions?
-pete
--
peter royal -> proyal@managingpartners.com
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Xalan CVS / Extension Functions / XSLTC
Posted by Peter Royal <pr...@managingpartners.com>.
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
name="selected">selected</xsl:attribute></xsl:if>
<xsl:apply-templates/>
</option>
</xsl:transform>
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.
-pete
--
peter royal -> proyal@managingpartners.com
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: Xalan CVS / Extension Functions / XSLTC
Posted by Stefano Mazzocchi <st...@apache.org>.
Peter Royal wrote:
>
> I downloaded the 04-04 CVS snapshot of Xalan-J and tried the XSLTC support,
> but gave me some error about finding a class Gomer... (that's not the exact
> error, but i stopped after that)..
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.
> BUT the latest Xalan is *MUCH* faster in interpreted mode (3x for the
> stylesheet i was trying to optimize)
Wow.
> *BUT* the extension function we use in
> xsp.xsl wasn't working correctly, I was just getting empty strings. I am thus
> running a modified xsp.xsl which removes use of the extension (I know my XSP
> sources will be fine w/o it).
>
> But the question is, I know I'm playing with fire with the Xalan CVS
> snapshot. Has anyone had any luck with the recent ones wrt XSLTC or the
> extension functions?
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.
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<st...@apache.org> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org