I should probably note that my main motivation in using JMS is so that we can guarantee that certain types of messages are processed. We will advertise HTTP endpoints to all of our clients, but internally we will use JMS to communicate from one WS to another. If our services are down, they can process the messages when they come back up. We'll be doing this mostly for fire and forget service calls.
jp4 wrote: > > Alessio, > > We dumped the JBossWS entirely in favor of CXF. I'm just trying to get > JMS integration working without having to modify our WSDLs. > Thanks, > > John > > > Alessio Soldano wrote: >> >> Hi John, >> if you're using the JBossWS-CXF stack, jms integration has not been >> addressed yet, sorry. >> Cheers >> Alessio >> >> jp4 wrote: >>> I am currently using cxf 2.2. I have several http endpoints (which are >>> generated from wsdl). These endpoints work great since dumping the >>> jboss >>> native stack! >>> >>> Now I'd like one of my endpoints to support both http as well as jms. >>> I've >>> read the cxf docs, but it's unclear whether or not I can do this without >>> modifying the WSDL. Ideally, I'd just like to configure another >>> endpoint >>> which listens on a request queue (and delegates to the endpoint that I >>> have >>> already configured in spring). >>> >>> I have the following configuration which throws the following exception >>> on >>> startup... I have configured the address="jms://". Can anyone point me >>> in >>> the right direction? >>> >>> Thanks, >>> >>> John >>> >>> Caused by: org.apache.cxf.configuration.ConfigurationException: You can >>> only >>> use JMSConfigFeature with the jms transport >>> at >>> org.apache.cxf.transport.jms.JMSConfigFeature.initialize(JMSConfigFeature.java:61) >>> >>> >>> <bean id="wsCtx" >>> class="org.apache.cxf.jaxws.context.WebServiceContextImpl"/> >>> >>> <jaxws:endpoint id="JMSSingleSignOnServicesImpl_1_0_0" >>> address="jms://" >>> >>> implementor="#singleSignOnServicesImpl_1_0_0"> >>> <jaxws:features> >>> <bean >>> class="org.apache.cxf.transport.jms.JMSConfigFeature" >>> p:jmsConfig-ref="jmsConfig" /> >>> </jaxws:features> >>> </jaxws:endpoint> >>> >>> <bean id="jndiConfig" >>> class="org.apache.cxf.transport.jms.JNDIConfiguration"> >>> <property name="environment"> >>> <props> >>> <prop >>> key="java.naming.factory.initial">org.apache.activemq.jndi.ActiveMQInitialContextFactory</prop> >>> <prop >>> key="java.naming.provider.url">tcp://localhost:61616</prop> >>> </props> >>> </property> >>> </bean> >>> >>> <bean id="wrappedConnectionFactory" >>> class="org.springframework.jms.connection.SingleConnectionFactory"> >>> <property name="targetConnectionFactory"> >>> <bean class="org.apache.activemq.ActiveMQConnectionFactory"> >>> <property name="brokerURL" >>> value="tcp://localhost:61616" /> >>> </bean> >>> </property> >>> </bean> >>> >>> <bean id="jmsConfig" >>> class="org.apache.cxf.transport.jms.JMSConfiguration" >>> p:jndiConfig-ref="jndiConfig" >>> p:connectionFactory-ref="wrappedConnectionFactory" >>> p:jndiTemplate-ref="jndiTemplate" >>> p:targetDestination="accountServicesRequestQueue" >>> p:replyDestination="accountServicesResponseQueue"> >>> </bean> >>> >> >> >> -- >> Alessio Soldano >> Web Service Lead >> JBoss, a division of Red Hat >> >> >> > > -- View this message in context: http://www.nabble.com/CXF-JMS-Integration-tp23767613p23782282.html Sent from the cxf-user mailing list archive at Nabble.com.
