On Mon June 29 2009 10:12:11 am nicolas de loof wrote: > I finally understood my mistake as CXF seems to expect the SOAP binding to > be <soap:binding style="document" transport=" > http://cxf.apache.org/transports/jms"/> > and not <soap:binding style="document" transport=" > http://schemas.xmlsoap.org/soap/j <http://schemas.xmlsoap.org/soap/http> > ms"/> > > Is the SOAP over JMS such an exotic feature that there is no framework > agnostic binding namespace ?
There is, but it was just "approved" about 4 weeks ago: http://www.w3.org/TR/2009/CR-soapjms-20090604/ We have a GSoC student implementing it for CXF, hopefully for CXF 2.3.0. Some of it was just merged to trunk this past weekend. Feel free to grab the snapshots if you are interested. That said, I'm not aware of any other stacks that implement the spec yet either since it's brand new. Dan > > Best regards, > Nicolas > > > > > 2009/6/29 nicolas de loof <[email protected]> > > > Hi, > > I'd like to expose my EndPoint as a JMS web service > > > > I've added cxf-rt-transport-jms JAR as dependency and updated my Spring > > configuration to user "jms://" URL as describe in CXF doc > > http://cwiki.apache.org/CXF20DOC/using-the-jmsconfigfeature.html > > > > <bean id="acteEndPoint" class="com....ActeEndPoint"/> > > > > <jaxws:endpoint id="acteEndPoint.jms" > > address="jms://" > > implementor="#acteEndPoint" > > > <jaxws:properties> > > <entry key="schema-validation-enabled" > > value="${ws.schema-validation-enabled}" /> > > </jaxws:properties> > > <jaxws:features> > > <bean class="org.apache.cxf.transport.jms.JMSConfigFeature"> > > <property name="jmsConfig"> > > <bean class="org.apache.cxf.transport.jms.JMSConfiguration" > > p:connectionFactory-ref="mqConnectionFactory" > > p:useJms11="true" > > > > > > p:targetDestination="queue://VPC_QMGR.D1/VGR/130/01/130_695/DET_OPECO_VPC > >/00/EV?targetClient=1" /> > > </property> > > </bean> > > </jaxws:features> > > </jaxws:endpoint> > > > > (Note : the JMS implementation I'm using is IBM Websphere MQ 6) > > > > > > Running the applicationContext fails : > > > > > > Caused by: javax.xml.ws.WebServiceException: > > org.apache.cxf.service.factory.ServiceConstructionException > > at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:275) > > ... 37 more > > Caused by: org.apache.cxf.service.factory.ServiceConstructionException > > at > > org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:1 > >39) at > > org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean > >.java:167) ... 46 more > > Caused by: java.net.MalformedURLException: unknown protocol: jms > > at java.net.URL.<init>(URL.java:574) > > at java.net.URL.<init>(URL.java:464) > > at java.net.URL.<init>(URL.java:413) > > at > > org.apache.cxf.transport.http_jetty.JettyHTTPDestination.<init>(JettyHTTP > >Destination.java:92) at > > org.apache.cxf.transport.http_jetty.JettyHTTPTransportFactory.createDesti > >nation(JettyHTTPTransportFactory.java:116) at > > org.apache.cxf.transport.http_jetty.JettyHTTPTransportFactory.getDestinat > >ion(JettyHTTPTransportFactory.java:103) at > > org.apache.cxf.endpoint.ServerImpl.initDestination(ServerImpl.java:90) at > > org.apache.cxf.endpoint.ServerImpl.<init>(ServerImpl.java:69) at > > org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:1 > >18) ... 49 more > > > > > > What did I missed ? > > > > Nicolas -- Daniel Kulp [email protected] http://www.dankulp.com/blog
