Mailing-List: contact beehive-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Beehive Users" <beehive-user@incubator.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: problem with SOAPMessage.class
Date: Wed, 23 Mar 2005 12:19:58 -0800
Message-ID: <4B2B4C417991364996F035E1EE39E2E102B0BDE4@uskiex01.amer.bea.com>
Thread-Topic: problem with SOAPMessage.class
Thread-Index: AcUv49ROzKkgYm8+RmSkNhOFkSs1KQAACsmQ
From: "Daryoush Mehrtash" <dmehrtas@bea.com>
To: "Beehive Users" <beehive-user@incubator.apache.org>

I am still trying to find why xml bean implementation of the soap
classes are packaged in XML Beans.  I think they should be packaged
separately.  I am still working on trying to resolve this with XML
Beans.

I am confused at your use case.  Do you have problem running annotated
and standard Axis web services under the same web application or do you
have the problem even if the annotated and non-annotated web services
are in different applications.

I expect that if you want to run annotated and standard web services
under the same web app then (for now until we figure out the xml beans
jar packaging) you should need is to remove the SAAJ.jar from the web
app's lib directory and then everything should work.

If you have the annotated and standard webservices running on two
different web apps, then there shouldn't be any problems.  It would make
sense to remove saaj.jar again from the web app that is running the
annotated web service.

May be the other explanation is that you have XML Beans even in your
non-annotated web services, otherwise why do you even include xml
beans's jar in your web app that is running the standard axis web
services.

Daryoush

-----Original Message-----
From: James Black [mailto:jblack@ieee.org]=20
Sent: Wednesday, March 23, 2005 12:06 PM
To: Beehive Users
Subject: Re: problem with SOAPMessage.class

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

Daryoush Mehrtash wrote:
| Have you tried removing SAAJ.jar?  And use the XMLBeans implementation
| of the java.xml.soap classes.

~  I have finally just copied saaj.jar to TOMCAT_DIR/common/lib and have
it removed from both webapps, and I removed SOAPMessage from
apache-xbeans.jar.

~  Now I can work on both types of webservices.

- --
"Love is mutual self-giving that ends in self-recovery." Fulton Sheen
James Black    james@usf.edu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCQcxDikQgpVn8xrARAmmBAJ9I2CF9FsGeWZW3wnWAfoyQW2blPACfW7op
aRcw9vKm90YfJvU5Ri67ufw=3D
=3D0VU0
-----END PGP SIGNATURE-----