Re: jms client restart
Adrian/Christian, I've been looking over the JMSConduit code. I believe we could solve this issue if we allowed for developers to inject their own JMS listener into the conduit. We have set up an interceptor to inject our own JMS correlation Id into the Message Object. If we had a way to inject our own consumer to the conduit we could manage the persistence and correlation of request/response messages. Let me know what you think. Thanks! -Chris Christian Schneider wrote: Hi Adrian, I think this can be done in CXF. I was talking more about what you do in the application layer and how you design your service. For example if your service call creates a customer object then you can simply return a generated customer id on success. In this case you need the correlation id to make sense of the reply. If you instead return the complete Customer data you just set including the customer id that was created while doing the call then you can probably process the reply without knowing the request that caused this reply. When doing loosely coupled asynchronous services it is very important to design like in the second example. Greetings Christian Adrian Corcoran schrieb: Hi Christian, So when you say that you have to write the client in a really asynchronous way are you saying you don't really think that there is a way that this can be done using CXF? Thanks, Adrian -- Christian Schneider --- http://www.liquid-reality.de -- View this message in context: http://www.nabble.com/jms-client-restart-tp20853766p20917773.html Sent from the cxf-user mailing list archive at Nabble.com.
Re: cxf Async with Spring - could not find wsdl:binding operation error
Has anyone figured out this issue? dan_pretty_boy wrote: Hi Folks, I am trying to call a webservice via spring asynchronously. now i have tried the normal way of calling an async method which works, but I would like to get it working in spring.. I am keep on getting the error could not find wsdl:binding operation info for web method testAsync, I think its to do with the JaxWsConfiguration.java isWebMethod(), in the code it excludes the Future and Response type and hence thats the reason why I am getting this error. Is there any reason why cxf is excluding this async methods. Has anyone got async working with spring, Any ideas? Regards Danny -- View this message in context: http://www.nabble.com/cxf-Async-with-Spring---could-not-find-wsdl%3Abinding-operation-error-tp18923398p20896770.html Sent from the cxf-user mailing list archive at Nabble.com.
Re: CXF JMS Asycn through Spring
Thanks for the response Dan! I've tried the jaxws:client approach and had the same result. I've attached a hello world example I threw together. If you look at the App.java, it starts an embedded broker, attempts to place a message on the queue with the Async method which immediately fails. It then tries to use the synchronous 'blocking' approach which does work, although the client will time out as there is no 'server' to pick the message of the queue. You will have to generate the wsdl source from the wsdl with Maven. Let me know what you think. http://www.nabble.com/file/p20906007/JmsAsyncTest.zip JmsAsyncTest.zip -- View this message in context: http://www.nabble.com/CXF-JMS-Asycn-through-Spring-tp20901403p20906007.html Sent from the cxf-user mailing list archive at Nabble.com.
