Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (asf.osuosl.org: local policy includes SPF record at
 spf.trusted-forwarder.org)
Mime-Version: 1.0 (Apple Message framework v622)
In-Reply-To: <57023d1305090903061af7198@mail.gmail.com>
References: <57023d1305090903061af7198@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <aec3acc4f402e594f23a340f517d7a4f@apache.org>
Content-Transfer-Encoding: quoted-printable
From: David Jencks <djencks@apache.org>
Subject: Re: [Axis2] Subtle yet serious issue
Date: Sat, 10 Sep 2005 17:28:44 -0700
To: axis-dev@ws.apache.org

I'm not entirely sure what the problem you are running into is, but I=20
recall some discussion on the xmlbeans list about something that sounds=20=

related to me.  I think that in xbean-2.0.0.jar the classes involved=20
have been moved into an xmlbeans package from the javax.xml.soap=20
package.  There are several other bug fixes in 2.0.0 that made it=20
usable in geronimo, so you may want to upgrade anyway.

thanks
david jencks


On Sep 9, 2005, at 3:06 AM, jayachandra wrote:

> Guys!
> I've identified this with great hardship trying to run some saaj=20
> related test kit.
> =A0
> The issue is, as a dependency for wsdl module (data binding) we are=20
> using xbean-2.0.0-beta1.jar. But **this jar has redefined=20
> javax.xml.soap package classes and the crucial of them=20
> SOAPMessageFactory.java, and SOAPFactory.java (abstract classes) are=20=

> pointing to axis 1.x version implementation classes in their=20
> newInstance() methods**
> So meaning, once the user deploys axis2 on tomcat, if this xbean jar=20=

> comes first in his classpath, then all the saaj specific=20
> implementation would be referring to axis1.x implementation and not=20
> our Axis2 org.apache.axis2.saaj.* implementation.
> =A0
> @Ajith!
> Do we need javax.xml.soap. package bundled along=A0with xbean jar, in=20=

> the first place. I don't know why xml beans was using saaj apis. If we=20=

> seriously need them, can we tweak the jar such that the existing=20
> harded coded values like "=20
> org.apache.axis.soap.SOAPMessageFactoryImpl" be modified to=20
> "org.apache.axis2.saaj.SOAPMessageFactoryImpl" and rehost the jar at=20=

> some alternate location. Or more better, we can build saaj prior to=20
> wsdl module and use axis2-saaj-${ pom.version}.jar along with the jar=20=

> containing core xmlbeans classes.
> =A0
> Thank you
> Jayachandra
> --=20
> -- Jaya=