Hello,
I'had not problems with JDK 1.4 and Xalan 1.7.
The xml-api in JDK 1.4 is too old for all newest xml implementation (xalan,
xerces ...)
You should try to update xml-api.
JAXP-RI provides all implementations of xalan, xerces, bcel, and stax in one
Jar. And another jar only for xml-apis (dom, sax, stream). Put the
api.jarin endorsed classpath and it should work fine now.
https://jaxp.dev.java.net/
hi,
>
> we have the following situation (and i already found out from the
> FAQ's and the mailing list that this is a known problem):
> - jdk 1.4
> - jibx
> - xalan (includes an old or at least incompatible version of bcel)
>
> you can guess that at compile time jibx goes down with a
> java.lang.IncompatibleClassChangeError.
>
> problem is, as Xalan is part of the JDK 1.4, we need tp put the newer
> version of Xalan into the <java-home>/lib/endorsed folder to be able
> to use this specific version of Xalan. JDK 1.4 is a production
> environment limitation, we cannot switch to a higher version of the
> JDK even in the dev envrionment.
>
> so Xalan with the "old" bcel version is something we cannot change,
> otherwise we cannot compile or run the application.
>
> but since we introduces Xalan to our application, jibx binding at
> compile time doesn't work anymore.
>
> does anyone have a solution for that? it seems that xalan and jibx
> exclude each other more or less....
>
> br,
> günther
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
jibx-users mailing list
jibx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jibx-users
