-
15. Re: WSContractConsumer API in a seam app
maeste Feb 27, 2007 3:59 PM (in response to maeste)some more infos hoping it help you to understand the problem. If I put also in loading Service class the try/finally block replacing the context class loader and restoring I get the previous problem: it works perfectly at first deploy, but after a redeployment I get this stack trace:
java.lang.reflect.InvocationTargetException 21:55:09,218 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 21:55:09,218 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 21:55:09,218 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 21:55:09,218 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585) 21:55:09,218 ERROR [STDERR] at it.javalinux.wise.jaxCore.WSDynamicClient.selectEndPoint(WSDynamicClient.java:189) 21:55:09,218 ERROR [STDERR] at it.javalinux.wise.seam.actions.WSDLManagerBean.readOperations(WSDLManagerBean.java:147) 21:55:09,218 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 21:55:09,218 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 21:55:09,218 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 21:55:09,218 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585) 21:55:09,218 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) 21:55:09,218 ERROR [STDERR] at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) 21:55:09,218 ERROR [STDERR] at org.jboss.seam.intercept.EJBInvocationContext.proceed(EJBInvocationContext.java:37) 21:55:09,218 ERROR [STDERR] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:55) 21:55:09,218 ERROR [STDERR] at org.jboss.seam.interceptors.BijectionInterceptor.bijectNonreentrantComponent(BijectionInterceptor.java:79) 21:55:09,218 ERROR [STDERR] at org.jboss.seam.interceptors.BijectionInterceptor.bijectComponent(BijectionInterceptor.java:58) 21:55:09,219 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 21:55:09,219 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 21:55:09,219 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 21:55:09,219 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585) 21:55:09,219 ERROR [STDERR] at org.jboss.seam.util.Reflections.invoke(Reflections.java:18) 21:55:09,219 ERROR [STDERR] at org.jboss.seam.intercept.Interceptor.aroundInvoke(Interceptor.java:169) 21:55:09,219 ERROR [STDERR] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:64) 21:55:09,219 ERROR [STDERR] at org.jboss.seam.interceptors.ManagedEntityIdentityInterceptor.aroundInvoke(ManagedEntityIdentityInterceptor.java:36) 21:55:09,219 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 21:55:09,219 ERROR [STDERR] Caused by: java.lang.NoClassDefFoundError: org/jboss/ws/core/soap/attachment/AttachmentPartImpl 21:55:09,219 ERROR [STDERR] at org.jboss.ws.core.jaxws.binding.BindingProviderImpl.initBinding(BindingProviderImpl.java:77) 21:55:09,219 ERROR [STDERR] at org.jboss.ws.core.CommonBindingProvider.<init>(CommonBindingProvider.java:55) 21:55:09,219 ERROR [STDERR] at org.jboss.ws.core.jaxws.binding.BindingProviderImpl.<init>(BindingProviderImpl.java:56) 21:55:09,219 ERROR [STDERR] at org.jboss.ws.core.jaxws.client.ClientImpl.getCommonBindingProvider(ClientImpl.java:293) 21:55:09,220 ERROR [STDERR] at org.jboss.ws.core.jaxws.client.ClientImpl.getBindingProvider(ClientImpl.java:315) 21:55:09,220 ERROR [STDERR] at org.jboss.ws.core.jaxws.client.ClientImpl.getRequestContext(ClientImpl.java:300) 21:55:09,220 ERROR [STDERR] at org.jboss.ws.core.jaxws.client.ClientImpl.setTargetEndpointAddress(ClientImpl.java:279) 21:55:09,220 ERROR [STDERR] at org.jboss.ws.core.jaxws.client.ClientImpl.<init>(ClientImpl.java:82) 21:55:09,220 ERROR [STDERR] at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.createProxy(ServiceDelegateImpl.java:328) 21:55:09,220 ERROR [STDERR] at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPortInternal(ServiceDelegateImpl.java:210) 21:55:09,220 ERROR [STDERR] at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:148) 21:55:09,220 ERROR [STDERR] at javax.xml.ws.Service.getPort(Service.java:116) 21:55:09,220 ERROR [STDERR] at it.javalinux.ws.MatchingService.getMatchingPort(MatchingService.java:56) 21:55:09,220 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 21:55:09,220 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 21:55:09,220 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 21:55:09,220 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585) 21:55:09,220 ERROR [STDERR] at it.javalinux.wise.jaxCore.WSDynamicClient.selectEndPoint(WSDynamicClient.java:189) 21:55:09,220 ERROR [STDERR] at it.javalinux.wise.seam.actions.WSDLManagerBean.readOperations(WSDLManagerBean.java:147) 21:55:09,220 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 21:55:09,220 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 21:55:09,221 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 21:55:09,221 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585) 21:55:09,221 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) 21:55:09,221 ERROR [STDERR] at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) 21:55:09,221 ERROR [STDERR] at org.jboss.seam.intercept.EJBInvocationContext.proceed(EJBInvocationContext.java:37) 21:55:09,221 ERROR [STDERR] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:55) 21:55:09,222 ERROR [STDERR] java.lang.NullPointerException: 21:55:09,222 ERROR [STDERR] at it.javalinux.wise.jaxCore.WSDynamicClient.getWebMethod(WSDynamicClient.java:200) 21:55:09,222 ERROR [STDERR] at it.javalinux.wise.seam.actions.WSDLManagerBean.readOperations(WSDLManagerBean.java:152) 21:55:09,222 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 21:55:09,222 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 21:55:09,222 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 21:55:09,222 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585) 21:55:09,222 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) 21:55:09,222 ERROR [STDERR] at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) 21:55:09,222 ERROR [STDERR] at org.jboss.seam.intercept.EJBInvocationContext.proceed(EJBInvocationContext.java:37) 21:55:09,222 ERROR [STDERR] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:55) 21:55:09,222 ERROR [STDERR] at org.jboss.seam.interceptors.BijectionInterceptor.bijectNonreentrantComponent(BijectionInterceptor.java:79) 21:55:09,222 ERROR [STDERR] at org.jboss.seam.interceptors.BijectionInterceptor.bijectComponent(BijectionInterceptor.java:58) 21:55:09,222 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 21:55:09,222 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 21:55:09,222 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 21:55:09,222 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585) 21:55:09,222 ERROR [STDERR] at org.jboss.seam.util.Reflections.invoke(Reflections.java:18) 21:55:09,222 ERROR [STDERR] at org.jboss.seam.intercept.Interceptor.aroundInvoke(Interceptor.java:169) 21:55:09,222 ERROR [STDERR] at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:64) 21:55:09,222 ERROR [STDERR] at org.jboss.seam.interceptors.ManagedEntityIdentityInterceptor.aroundInvoke(ManagedEntityIdentityInterceptor.java:36) 21:55:09,222 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 21:55:09,222 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 21:55:09,222 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 21:55:09,222 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585) 21:55:09,222 ERROR [STDERR] at org.jboss.seam.util.Reflections.invoke(Reflections.java:18) 21:55:09,222 ERROR [STDERR] at org.jboss.seam.intercept.Interceptor.aroundInvoke(Interceptor.java:169)
thanks for your time -
16. Re: WSContractConsumer API in a seam app
jason.greene Feb 27, 2007 11:32 PM (in response to maeste)This problem might be unrelated to the classloader. Can you try taking the generated classes and include them in your deployment?
-Jason -
17. Re: WSContractConsumer API in a seam app
maeste Feb 28, 2007 7:28 AM (in response to maeste)"jason.greene@jboss.com" wrote:
This problem might be unrelated to the classloader. Can you try taking the generated classes and include them in your deployment?
Uch you are right. I removed any dynamic class generation and addedthe generated source to the deployment. Now the init method of my class lokks like:serviceClass = MatchingService.class; service = serviceClass.newInstance();
And I get the same behaviour of my last post.
So you are right it isn't a problem with classloader. But now I'm a bit confused: what is going wrong with hot deployment?
Thanks -
18. Re: WSContractConsumer API in a seam app
jason.greene Feb 28, 2007 10:01 AM (in response to maeste)What version of JBossAS and JBossWS are you running on?
-
19. Re: WSContractConsumer API in a seam app
maeste Feb 28, 2007 10:13 AM (in response to maeste)jboss 4.05 and jbossws from svn trunk. Seam 1.1.6
thanks -
20. Re: WSContractConsumer API in a seam app
jason.greene Feb 28, 2007 12:45 PM (in response to maeste)Perhaps this is a seam issue. Can you try hot redeploy using a plain servlet instead of seam?
-
21. Re: WSContractConsumer API in a seam app
maeste Feb 28, 2007 2:48 PM (in response to maeste)no luck,
exactly the same Exception.
Thanks for your time. -
22. Re: WSContractConsumer API in a seam app
jason.greene Feb 28, 2007 3:04 PM (in response to maeste)This has to be a bug on our end then. I created an issue here:
http://jira.jboss.com/jira/browse/JBWS-1540
I will take a look at it this week, but if you happen to uncover anything before then please add any details to the jira issue.
-Jason -
23. Re: WSContractConsumer API in a seam app
maeste Feb 28, 2007 3:08 PM (in response to maeste)Do you need an example uploaded to Jira?
-
24. Re: WSContractConsumer API in a seam app
jason.greene Feb 28, 2007 3:10 PM (in response to maeste)Sure that would help alot actually.
Thanks!,
-Jason -
25. Re: WSContractConsumer API in a seam app
maeste Feb 28, 2007 4:17 PM (in response to maeste)done.
If you need any clarification feel free to contact me also with skype (I'm sending you a private mail with my contact)
Thanks for the interest. -
26. Re: WSContractConsumer API in a seam app
jason.greene Mar 1, 2007 8:15 PM (in response to maeste)I wasn't able to reproduce the problem since the attached deployment was referencing a WSDL file that wasn't present. However, I noticed that the jbossws jars are included in the ear file. this could lead to issues and possible conflicts. Can you try pulling the jboss jars out of the deployment, and just relying on the ones in container? If they aren't available copy the few that are missing into the server/lib directory.
-
27. Re: WSContractConsumer API in a seam app
maeste Mar 2, 2007 11:53 AM (in response to maeste)Ok, I get it work finally.
Problem was solved removing most part of jbossws jars (leave there only jbossws-wsconsume-impl.jar and jaxb-xjc.jar that stay in client dir in the server).
I putted all jars inside the ear because it is the suggested way for seam apps and simplify distribution and deploy.
Sincerely I didn't understand what happened to classLoader in hot deploying jbossws' jars.
Thanks a lot for the interest.
I think our generic client based on wsConsumer will be released in few days. Thanks for your help.