From: Kevin Ross (Kevin.Ross@iVerticalLeap.com)
Date: Tue Apr 29 2003 - 10:33:02 PDT
Great! Thanks, that clears it up, I was unclear that XT would be used
as internal only, and not for the xsl->xsl:fo transformation
-----Original Message-----
From: owner-xep-support@www.renderx.com
[mailto:owner-xep-support@www.renderx.com] On Behalf Of David Tolpin
Sent: Tuesday, April 29, 2003 8:58 AM
To: xep-support@renderx.com
Subject: Re: [xep-support] XEP 3 + XALAN
>
> >>it still uses XT for internal purposes,
> >>because it is faster and smaller. Usually many times faster
> >>and smaller than XALAN.
>
> Even so, it is more important to me to be functional, than fast, and I
> have code that works with Xalan, where I've had no luck with XT after
> many hours.
>
> So the previous message stating, "XEP is JAXP-aware" is not entirely
> true?
>
> Would it be possible to get a patch that allows me to use a JAXP
> transformer?
>
Kevin,
please read the documentation.
XEP is JAXP-aware. It uses both a JAXP-compliant component to load
SAX parser and call XSLT transformer for xml+xsl->fo transformation
and XT for its internal purposes.
You have to have both XALAN and XT in the path. XT is an immanent
part of XEP. It is not used for xml+xsl->fo transformations.
David Tolpin
-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo@renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service
http://www.renderx.com/tos.html
-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo@renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/tos.html
This archive was generated by hypermail 2.1.5 : Tue Apr 29 2003 - 09:23:19 PDT