On Wed, Jan 26, 2011 at 12:00 AM, Wally Dennis <wally.den...@aonhewitt.com> wrote: > > 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?
I used the same approach to get around the problem. There is a JIRA[1] describing this behaviour. (and possible approaches to overcome this) [1] https://issues.apache.org/jira/browse/AXIS2-4917 --Pradeep --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org For additional commands, e-mail: java-user-h...@axis.apache.org
