No, use the SOAP/JMS spec stuff. That's a standard form that we should be promoting instead of the proprietary stuff.
Jan: can you create a small test case? We can take a look easier then. Not really sure what is going on yet. Dan On Aug 16, 2013, at 5:56 AM, Christian Schneider <[email protected]> wrote: > Try to use the jmsConfigFeature. The wsdl configuration is still quite fresh > and I do not know if it can handle your case. > Additionally how would you externalize the queue name and other configs into > config admin properties when using wsdl config? > > Christian > > > Am 16.08.2013 09:29, schrieb janb: >> Here is the part from my wsdl: >> >> <wsdl:binding name="CRMServiceJMSBinding" type="tns:CRMService"> >> <soap:binding style="document" >> transport="http://www.w3.org/2010/soapjms/"; /> >> >> <soapjms:jndiConnectionFactoryName>ConnectionFactory</soapjms:jndiConnectionFactoryName> >> >> <soapjms:jndiInitialContextFactory>org.apache.activemq.jndi.ActiveMQInitialContextFactory</soapjms:jndiInitialContextFactory> >> <soapjms:jndiURLtcp://localhost:61616</soapjms:jndiURL> >> <wsdl:operation name="getCRMStatus"> >> <soap:operation soapAction="getCRMStatus"/> >> <wsdl:input> >> <soap:body use="literal"/> >> </wsdl:input> >> <wsdl:output> >> <soap:body use="literal"/> >> </wsdl:output> >> </wsdl:operation> >> </wsdl:binding> >> >> <wsdl:service name="CRMServiceProvider"> >> <wsdl:port binding="tns:CRMServiceJMSBinding" >> name="CRMServiceJMSQueuePort"> >> <soap:address >> location="jms:queue:queue.CRM.REQUEST?replyToName=queue.CRM.RESPONSE&timeToLive=100000" >> /> >> </wsdl:port> >> <wsdl:port binding="tns:CRMServiceJMSBinding" >> name="CRMServiceJMSTopicPort"> >> <soap:address location="jms:topic:topic.CRM.REQUEST" >> /> >> </wsdl:port> >> <wsdl:port binding="tns:CRMServiceBinding" >> name="CRMServicePort"> >> <soap:address >> location="http://localhost:8040/services/CRMServiceProvider/"/> >> </wsdl:port> >> </wsdl:service> >> >> Regards. >> Jan >> >> From: cschneider [via CXF] [mailto:[email protected]] >> Sent: Freitag, 16. August 2013 09:06 >> To: Jan Bernhardt >> Subject: Re: JMS Topic Support with Response is not working >> >> Hi Jan, >> >> the addresses you mention look like camel addresses. Are you using pure >> cxf or the camel cxf component? >> >> Christian >> >> Am 15.08.2013 17:53, schrieb janb: >> >>> Hi all, >>> >>> I'm using JMS transport for SOAP Webservices the first time. And I got my >>> demo project working without any problems if I use a queue. However if I use >>> a topic, my webservice is called but never returns any response back even >>> thou there is a replyTo address set within the JMS message. The CXF client >>> is even listening on that queue or/and topic, but the server is not sending >>> any messages back so my client raises an timeout exception. >>> >>> Here are the addresses I used which have been working: >>> jms:queue:queue.MY.REQUEST >>> jms:queue:queue.MY.REQUEST?replyToName=queue.MY.RESPONSE&timeToLive=100000 >>> jms:queue:queue.MY.REQUEST?topicReplyToName=topic.MY.RESPONSE >>> >>> And here are the addresses I used which are not working: >>> jms:topic:topic.MY.REQUEST >>> jms:topic:topic.MY.REQUEST?replyToName=queue.CRM.RESPONSE >>> jms:topic:topic.MY.REQUEST?topicReplyToName=topic.MY.RESPONSE >>> >>> For me this looks like a BUG (I used 2.7.5 and 2.7.7-SNAPSHOT for testing). >>> Can someone confirm this? >>> >>> Best regards. >>> Jan >>> >>> >>> >>> -- >>> View this message in context: >>> http://cxf.547215.n5.nabble.com/JMS-Topic-Support-with-Response-is-not-working-tp5732525.html >>> Sent from the cxf-user mailing list archive at Nabble.com. >> >> -- >> >> Christian Schneider >> http://www.liquid-reality.de >> >> Open Source Architect >> Talend Application Integration Division http://www.talend.com >> >> >> ________________________________________ >> If you reply to this email, your message will be added to the discussion >> below: >> http://cxf.547215.n5.nabble.com/JMS-Topic-Support-with-Response-is-not-working-tp5732525p5732543.html >> To unsubscribe from JMS Topic Support with Response is not working, click >> here. >> NAML >> >> >> >> >> -- >> View this message in context: >> http://cxf.547215.n5.nabble.com/JMS-Topic-Support-with-Response-is-not-working-tp5732525p5732545.html >> Sent from the cxf-user mailing list archive at Nabble.com. > > > -- > Christian Schneider > http://www.liquid-reality.de > > Open Source Architect > Talend Application Integration Division http://www.talend.com > -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
