|
Hi all, for all who have problems
with AXIS and websphere 5.0 (5.1?). I have solved my problem
with saaj.jar and the incompatibleClassChangeError Exception. Im not able to tell you
the correct words for settings, because my WASD is in german, so I have to Translate the words. You have to set in
Classpath the path of the new saaj.jar delivered with AXIS 1.2 RC1 You have to set in Websphere-specific-classpath���
and in The regular classpath I must set both -
otherwise it will not work and I get this incompatible..... Hope this helps anybody Von: Tom Jordahl
[mailto:[EMAIL PROTECTED] Thomas, You must load the Axis
1.2 jar files first. Axis 1.2 implements the JAX-RPC 1.1 and SAAJ 1.2
specifications. Obviously there was an incompatible change in these
interfaces (in SAAJ 1.2 I believe). I ran in to this also, and had to do
some class loader voodoo to make sure that all the
javax.xml.{soap,rpc,messaging} classes get loaded from the Axis jars. Unfortunately I can't
tell you exactly how to fix your problem because my app has its own
(configurable) class loader. -- -----Original Message----- Developers of AXIS, We are facing the following problem: We use AXIS with websphere 5.1 and got a java.lang.IncompatibleClassChangeError. I have learned form the
user-list that this error comes with the new saaj.jar (AXIS 1.2 RC1). There is no problem with the
older Version of saaj.jar (AXIS 1.2 beta 1 & 2). So my question is: Is it possible to use the
new AXIS 1.2 RC1 with older saaj.jar and recompile my classes for websphere? �
Because websphere use intern an older saaj.jar and I can�t tell websphere to
ignore his own saaj.jar! Or will I get some error in
the future when using older saaj.jar??? Thanks for your efforts Thomas |
