Your cxf webservice provider defined by ELMdb.wsdl probably as a returned message. So when this webservice is invoked, e response is received and send back to the jms consumer who don't know where to send this response back to.
So when configuring a request/response exchange with jms you must provide both : - a destinationName (to handle the request message) : either with attribute jndiDestinationName or jmsProviderDestinationName - a replyDestinationName (to handle the response) : either with attribute jndiReplyToName or jmsProviderReplyToName Am I clear ? Manuel On Thu, Jul 24, 2008 at 12:43 PM, Håkon Sagehaug <[EMAIL PROTECTED]> wrote: > Hi > > I did this, with the configuration like this > > <jms:provider service="hsa:QueueProvider" > endpoint="QueueProvider" > destinationName="myQueue" > connectionFactory="#connectionFactory" > /> > > <jms:consumer service="hsa:ConsumerService" > endpoint="QueueConsumer" > destinationName="myQueue" > connectionFactory="#connectionFactory" > concurrentConsumers="8" > targetEndpoint="ELMdbProxy" > targetService="edb:ELMdb" > targetInterface="edb:ELMdb"/> > > and cxf like this > > <cxfbc:consumer wsdl="classpath:ELMdb.wsdl" > endpoint="ELMdb" > service="edb:ELMdb" > targetEndpoint="QueueProvider" > targetService="hsa:QueueProvider" > busCfg="cxf-validateEDB.xml" > > > </cxfbc:consumer> > > > <cxfbc:provider wsdl="classpath:ELMdb.wsdl" > locationURI="http://api.bioinfo.no/services/ELMdb"; > endpoint="ELMdbProxy" > service="edb:ELMdb" > interfaceName="edb:ELMdb" > busCfg="cxf-configEDB.xml" > > > </cxfbc:provider> > > But then I got the error java.lang.IllegalStateException: Unable to choose > replyDestination for exchange > > So I see a tip on the mailing list about adding the attribute > 'replyDestinationName', but not sure if it's the jms provider or the > consumer that needs it, tried both, but with no luck. And waht value is it > suppose to have the cxf-consumer > > cheers, Håkon > > > 2008/7/24 Guillaume Nodet <[EMAIL PROTECTED]>: > > > You need to have the following flows: > > cxf-consumer -> jms-provider -> jms-consumer -> cxf-provider > > > > The jms endpoints can be configured as explained at > > http://servicemix.apache.org/servicemix-jms-new-endpoints.html > > > > You can put both JMS endpoints in a single SU and share the same > > connection factory. > > > > As for the wiring, the cxf-consumer needs to point to the jms-provider > > endpoint, the jms-consumer points to cxf-provider, and both jms > > endpoints need to use the same JMS queue. > > > > On Thu, Jul 24, 2008 at 10:36 AM, Håkon Sagehaug <[EMAIL PROTECTED]> > > wrote: > > > Hi > > > > > > I want to have a flow like this, I've got the web service end points > but > > > wont to enhance with the jms reliability. > > > > > > cxf-consumer -> jms-queue -> cxf-provider > > > > > > So I'm wondering how to configure it all. I assume the cxf-consumer > must > > > point to a jms-queue, but is this a jms provider or a consumer and does > > the > > > cxf-provider need to point to a jms component?? > > > > > > I'm abit confused > > > > > > cheers, Håkon > > > > > > > > > -- > > > Håkon Sagehaug, Software Developer > > > Parallab, Bergen Center for Computational Science (BCCS) > > > UNIFOB AS (University of Bergen Research Company) > > > > > > > > > > > -- > > Cheers, > > Guillaume Nodet > > ------------------------ > > Blog: http://gnodet.blogspot.com/ > > > > > > -- > Håkon Sagehaug, Software Developer > Parallab, Bergen Center for Computational Science (BCCS) > UNIFOB AS (University of Bergen Research Company) >
