Re: [jboss-user] [JBoss Web Services CXF] - XTS tests broken in AS trunk after switch to CXF stack in 3.3.0
by Andrew Dinn
Andrew Dinn [http://community.jboss.org/people/adinn] replied to the discussion
"XTS tests broken in AS trunk after switch to CXF stack in 3.3.0"
To view the discussion, visit: http://community.jboss.org/message/547114#547114
--------------------------------------------------------------
Ok, I updated all my enpoint beans to include @Action annotations but I am still seeing some really weird stuff happening when messages are being delivered to endpoints. Here is an example:
> 15:38:04,038 INFO [STDOUT] KEV: processing SOAP action http://fabrikam123.com/InitiatorPortType/Response
> 15:38:04,067 ERROR [org.jboss.wsf.common.invocation.InvocationHandlerJAXWS] Method invocation failed with exception: com.jboss.transaction.txinterop.webservices.atinterop.sei.ParticipantPortTypeImpl.response(): java.lang.NoSuchMethodException: com.jboss.transaction.txinterop.webservices.atinterop.sei.ParticipantPortTypeImpl.response()
> at java.lang.Class.getMethod(Class.java:1605) [:1.6.0_14]
> at org.jboss.wsf.common.invocation.AbstractInvocationHandler.getImplMethod(AbstractInvocationHandler.java:92) [:1.3.0.GA]
> at org.jboss.wsf.common.invocation.AbstractInvocationHandlerJSE.invoke(AbstractInvocationHandlerJSE.java:122) [:1.3.0.GA]
> at org.jboss.wsf.stack.cxf.AbstractInvoker._invokeInternal(AbstractInvoker.java:154) [:3.3.0.GA]
> at org.jboss.wsf.stack.cxf.AbstractInvoker.invoke(AbstractInvoker.java:104) [:3.3.0.GA]
> at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:58) [:2.2.8]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_14]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [:1.6.0_14]
> at java.util.concurrent.FutureTask.run(FutureTask.java:138) [:1.6.0_14]
> at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37) [:2.2.8]
> at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:106) [:2.2.8]
> at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243) [:2.2.8]
> at org.apache.cxf.phase.PhaseInterceptorChain.resume(PhaseInterceptorChain.java:218) [:2.2.8]
> at org.apache.cxf.ws.addressing.ContextUtils$1.run(ContextUtils.java:420) [:2.2.8]
> at org.apache.cxf.workqueue.AutomaticWorkQueueImpl$2.run(AutomaticWorkQueueImpl.java:253) [:2.2.8]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_14]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_14]
> at java.lang.Thread.run(Thread.java:619) [:1.6.0_14]
>
Now this is rather weird because the message with action http://fabrikam123.com/InitiatorPortType/Response http://fabrikam123.com/InitiatorPortType/Response is never sent to the Participant service implemented by class ParticipantPortTypeImpl. Not surprisingly given the action definition it is sent to service Initiator implemented by class InitiatorPortTypeImpl. So, mmy code is sending messages to one service and they are being delivered to another service. Of course when running on trunk with native a few weeks back this worked fine. Also when I last tested it on a CXF build some months back it worked fine.
I will try to debug the code path through to AbstractInvocationHandler.getImplMethod() in order to see why it is looking at the wrong class and get back with any info I can find.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/547114#547114]
Start a new discussion in JBoss Web Services CXF at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years
Re: [jboss-user] [JBoss Web Services CXF] - XTS tests broken in AS trunk after switch to CXF stack in 3.3.0
by Andrew Dinn
Andrew Dinn [http://community.jboss.org/people/adinn] replied to the discussion
"XTS tests broken in AS trunk after switch to CXF stack in 3.3.0"
To view the discussion, visit: http://community.jboss.org/message/547083#547083
--------------------------------------------------------------
> Andrew Dinn wrote:
> I will try rebuilding the app with the latest published wsdl i.e. without the Action attributes in the wsdl. However, even if this does work the question is whether CXF ought to handle actions registered using the 2005/08 namespace. There may be other apps out there with out of date wsdl.
I rebuilt the services with all wsa:Action attributes removed from the WSDL and the Activation Service is now handing out contexts again.
However, now I am running into problems because messages to the other WS-TX services (and also to my test services) are being misdirected. I think this is probably because there is no longer any Action specified in the WSDL -- CXF appears to be directing the messages to servers based on the message content type. I will try adding @Action annotations to all the other service endpoint implementation methods to see if this resolves the problem.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/547083#547083]
Start a new discussion in JBoss Web Services CXF at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
16 years