axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Veithen <>
Subject Re: Jar file dependencies, specifically for geronimo-stax-api_1.0_spec-1.0.1.jar
Date Wed, 28 Sep 2011 19:07:45 GMT
Removing geronimo-stax-api_1.0_spec-1.0.1.jar is safe, but you should
double check that after removing that JAR, Axis2 is still using the
Woodstox StAX implementation and not the one provided by the server
runtime (WebSphere's XLXP parser is supported, but less well tested
than Woodstox, and WebLogic's StAX implementation is currently not

Regarding the dependencies: the page from the Rampart Web site is
generated from the Maven metadata. This is feasible for Rampart
because Rampart only has a single set of dependencies. For Axis2 it is
not realistic to publish that information because the project is split
into multiple Maven modules and each Maven module can have specific


On Tue, Sep 27, 2011 at 14:27, William Walsh <> wrote:
> Hi,
> We are deploying Axis2 web services in WebSphere and WebLogic and are seeing an application
conflict (JVMVRFY013 class loading constraint violated) with geronimo-stax-api_1.0_spec-1.0.1.jar
and are trying to determine the impact, if any, of removing this jar.  As far as I can tell
both WebSphere and WebLogic provide their own implementations of these classes (in xml.jar
and wlfullclient.jar, respectively).  But, am wondering if there might be future impacts
if we remove this jar.  In researching what the dependencies are I see that Rampart does
a very good job of defining its dependencies (see,
but I haven't been able to find anything for Axis2 in general.  Our testing hasn't revealed
any issues so far.  Does anyone have any experience or knowledge in this area of geronimo-stax-api_1.0_spec-1.0.1.jar
usage and/or dependencies that they could share?
> Thanks,
> William
> The information in this email is confidential and may be legally privileged.
> It is intended solely for the addressee. Access to this email by anyone else
> is unauthorized. If you are not the intended recipient, any disclosure,
> copying, distribution or any action taken or omitted to be taken in reliance
> on it, is prohibited and may be unlawful. If you are not the intended
> addressee please contact the sender and dispose of this e-mail. Thank you.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message