Nice job guys. Glad to see it all working. :-) Next question: Should the original page that Benson stole the demo from: http://cxf.apache.org/docs/jax-ws-java-first-with-jms-transport.html be updated with the new demo or should we wait until after 2.3 is released?
Dan On Monday 20 September 2010 7:21:56 am Benson Margulies wrote: > Thanks, all that makes sense. > > On Sun, Sep 19, 2010 at 11:47 PM, Willem Jiang <[email protected]> wrote: > > On 9/20/10 8:00 AM, Benson Margulies wrote: > >> That doesn't change the strange 'no endpoint' error. Do you have any > >> hints for how to track this down, or do you JMS hackers want to pick > >> up from here? > > > > The no endpoint error is caused by you set a wrong PortName :) > > As the SEI doesn't have the @WebService annotation, CXF will try to setup > > PortName which is based on the package and class name. > > > > After resolve this issue, I caught another snail which the Soap Over JMS > > namespace is missed from the DEFAULT_NAMESPACES of SoapBindingFactory. > > > > Now the JMSClient is working like a charm. > > > > BTW, I don't think we need the ClientHTTP.java and ServerHTTP.java any > > more, so I'm planing to remove them. > > > > Willem > > > >> On Sun, Sep 19, 2010 at 7:32 PM, Daniel Kulp<[email protected]> wrote: > >>> On Sunday 19 September 2010 7:20:12 pm Benson Margulies wrote: > >>>> Or, perhaps you prefer to answer this question: > >>>> > >>>> service.addPort(PORT_QNAME, SOAPBinding.SOAP11HTTP_BINDING, > >>>> JMS_ENDPOINT_URI); > >>>> > >>>> looks wrong. But what should I pass? What is the binding ID for > >>>> SOAP/JMS? > >>> > >>> I THINK you could use either of the SOAP id's: > >>> > >>> http://schemas.xmlsoap.org/wsdl/soap/ > >>> http://schemas.xmlsoap.org/wsdl/soap12/ > >>> > >>> depending on what version you want. > >>> > >>> > >>> Dan -- Daniel Kulp [email protected] http://dankulp.com/blog
