From: David Tolpin (email@example.com)
Date: Tue Apr 29 2003 - 07:58:21 PDT
> >>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
> Would it be possible to get a patch that allows me to use a JAXP
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.
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to firstname.lastname@example.org 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 - 07:48:13 PDT