[jboss-user] [JBoss Web Services] - Re: JAXWS error on jboss 6.0

[Jayaram Pradhan]

Jayaram Pradhan [https://community.jboss.org/people/jayaramimca] created the discussion

"Re: JAXWS error on jboss 6.0"

To view the discussion, visit: https://community.jboss.org/message/727609#727609

--------------------------------------------------------------
Hi Alessio,

I tried with jaxws stack as well with jbossws-metro stack, where as I am finding the below exception for both the cases:

05:46:00,756 INFO  [STDOUT] Caused by: java.lang.LinkageError: loader constraint violation: loader (instance of org/jboss/web/tomcat/service/WebCtxLoader$ENCLoader) previously initiated loading for a different type with name "javax/xml/soap/AttachmentPart"
05:46:00,756 INFO  [STDOUT]           at java.lang.Class.forName0(Native Method)
05:46:00,756 INFO  [STDOUT]           at java.lang.Class.forName(Class.java:169)
05:46:00,756 INFO  [STDOUT]           at $Proxy296.<clinit>(Unknown Source)
05:46:00,756 INFO  [STDOUT]           at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
05:46:00,757 INFO  [STDOUT]           at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
05:46:00,757 INFO  [STDOUT]           at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
05:46:00,757 INFO  [STDOUT]           at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
05:46:00,757 INFO  [STDOUT]           at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:588)
05:46:00,757 INFO  [STDOUT]           at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.createProxy(ServiceDelegateImpl.java:406)
05:46:00,757 INFO  [STDOUT]           at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPortInternal(ServiceDelegateImpl.java:243)
05:46:00,757 INFO  [STDOUT]           at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:570)
05:46:00,757 INFO  [STDOUT]           at javax.xml.ws.Service.getPort(Service.java:99)
05:46:00,758 INFO  [STDOUT]           at org.springframework.remoting.jaxws.JaxWsPortClientInterceptor.getPortStub(JaxWsPortClientInterceptor.java:413)
05:46:00,758 INFO  [STDOUT]           at org.springframework.remoting.jaxws.JaxWsPortClientInterceptor.prepare(JaxWsPortClientInterceptor.java:337)
05:46:00,758 INFO  [STDOUT]           at org.springframework.remoting.jaxws.JaxWsPortClientInterceptor.afterPropertiesSet(JaxWsPortClientInterceptor.java:316)
05:46:00,758 INFO  [STDOUT]           at org.springframework.remoting.jaxws.JaxWsPortProxyFactoryBean.afterPropertiesSet(JaxWsPortProxyFactoryBean.java:42)
05:46:00,758 INFO  [STDOUT]           at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1503)
05:46:00,758 INFO  [STDOUT]           at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1441)
05:46:00,758 INFO  [STDOUT]           ... 104 more

By looking at the stack trace can tell that its entering to jaxwsportproxy of spring to instansiate the bean.

and the issue of linkage error, I thought May be jar miss match from my src jar and webinf/lib directory of saj-api and saj-impl, I updated both with same version as well added javaxactivation.jar to the web-inf/lib still stuck on the same issue of linkage error.

I am sure I m getting close for this. Could you please let me suggest any option to overide the linkage issue ?

Thanks,
Jayaram.
--------------------------------------------------------------

Reply to this message by going to Community
[https://community.jboss.org/message/727609#727609]

Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2044]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-user/attachments/20120331/af4be07d/attachment-0001.html