-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chris,

Chris Mannion wrote:
| I'm not sure this is exactly the place to be asking but I can't think of
| anywhere else so here goes.  I have the same piece of code running on two
| different Tomcat installations, one Tomcat 5.0, the other Tomcat 5.5.  The
| code calls and web service and produces a javax.xml.soap.SOAPMessage in
| response.  Having noticed a slight difference in behaviour I debugged and
| found that on the Tomcat 5.0 system the underlying implementations of the
| javax.xml.soap interfaces (SOAPBody, SOAPElement etc.) were Axis classes
| such as org.apache.axis.message.SOAPBody.  On the Tomcat 5.5 system the
| underlying implementations are all from a
| com.sun.xml.internal.messaging.saaj.soap.impl package.

I don't believe Tomcat ships with any SOAP classes at all. Are you using
any 3rd-party JARs in either install (like AXIS)? Alternatively, are you
using different versions of JWSDK or anything like that? How about
different JVM versions?

| My question is what would be causing this difference, I thought perhaps
| libraries in Tomcat but have tried replacing all my libraries on
| Tomcat 5.0(including common, endorsed and those in the webapp) with
| those from Tomcat
| 5.5 but that didn't make any difference.

Er, you should undo that. ;)

| Has anyone got any more ideas?

I would find out where the classes themselves are being loaded. Check
your app's WEB-INF/lib directory, Tomcat's common/lib, shared/lib and
endorsed directories, and your JVMs "endorsed" directories, too.

- -chris

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkeOf9IACgkQ9CaO5/Lv0PAufwCdFoFQtpuTyFSmceKL5syDMa79
keoAnRrSe8DJdOf7wrKeuKVQyqbsZzr2
=IQjn
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to