Thanks for the test case. Big help. Basically, we're only binding the Async methods in when the client is created with a wsdl at runtime. In your case, it's not using the wsdl. If you add a wsdlLocation attribute to specify the location of the wsdl, it would probably work.
That said, it's definitely a bug and I have a fix that I'm going to test overnight and hopefully commit in the morning. Dan On Monday 08 December 2008 6:41:44 pm cxfuser17 wrote: > 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 -- Daniel Kulp [EMAIL PROTECTED] http://dankulp.com/blog
