Hi, Andrew,
Thanks for that hint, I wasn't aware of that system property
"javax.xml.transform.TransformerFactory". But I haven't used that yet,
so it still must be the xalan transformer I'm using. What else may be
the cause for my problem?
Ciao!
Kai
Andrew Welch schrieb:
On 6/15/07, Julian Reschke <julian(_dot_)reschke(_at_)gmx(_dot_)de> wrote:
Kai Hackemesser wrote:
> Hello!
>
> I have the strange case that a xsl transformation (XSL 1.0) output
looks
> different between an application running in JDK1.4.2 and JDK 1.5.0. In
> ...
I wouldn't call that "strange" at all. The two JDKs have completely
different XSLT engines, and they have different sets of bugs (Xalan vs
XSLTC).
Doesn't it depend on how the transformation was invoked? If it was
using JAXP then Xalan would still be used:
http://xml.apache.org/xalan-j/xsltc_usage.html#api
Afaik, you have to be explicit if you want to use xsltc.
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--