We are getting classloading conflicts when trying to deploy Axis2 1.5.3 on 
Websphere 7, Fixpack 13 that are preventing the addressing-1.5.3.mar from 
loading:


[1/24/11 18:53:53:765 CST] 00000030 ModuleDeploye E 
org.apache.axis2.deployment.ModuleDeployer deploy The addressing-1.5.3.mar 
module, which is not valid, caused 
org.apache.axis2.handlers.addressing.AddressingInHandler cannot be cast to 
org.apache.axis2.engine.Handler 
                                 java.lang.ClassCastException: 
org.apache.axis2.handlers.addressing.AddressingInHandler cannot be cast to 
org.apache.axis2.engine.Handler 

The issue appears to be that the classloader is pulling the 
AddressingInHandler from the org.apache.axis2.jar bundled with Websphere 
and won't load the one in the .mar file.  We have set all of the 
classloader policies to PARENT_LAST and also disabled JAX-WS support in 
Websphere.  The only way we have been able to get past this error is to 
copy the addressing-1.5.3.mar into our WEB-INF/lib directory and change 
the extension to .jar so that the classloader at least loads the right 
code before pulling it from WAS.

Has anyone been able to resolve this or get around it a different 
approach?

Thanks,
Wally



The information contained in this e-mail and any accompanying documents may 
contain information that is confidential or otherwise protected from 
disclosure. If you are not the intended recipient of this message, or if this 
message has been addressed to you in error, please immediately alert the sender 
by reply e-mail and then delete this message, including any attachments. Any 
dissemination, distribution or other use of the contents of this message by 
anyone other than the intended recipient is strictly prohibited. All messages 
sent to and from this e-mail address may be monitored as permitted by 
applicable law and regulations to ensure compliance with our internal policies 
and to protect our business. E-mails are not secure and cannot be guaranteed to 
be error free as they can be intercepted, amended, lost or destroyed, or 
contain viruses. You are deemed to have accepted these risks if you communicate 
with us by e-mail. 


Reply via email to