Guillaume, Thanks for the tip. For the JMS provider endpoint, is there a destinationChooser object that will create a temporary queue and set it as the replyDestination? I think the old JMS enpoint has this logic built-in. Thanks again.
gnodet wrote: > > The default marshaler for the <jms:consumer /> endpoint is configured to > create an InOnly exchange, but there is a property you can set to create > any other MEP. > Try something like: > > <jms:consumer service="my:ConsumerService" > endpoint="jbi" > destinationName="my.queue" > connectionFactory="#connectionFactory" > marshaler="#marshaler" /> > <bean id="marshaler" class=" > org.apache.servicemix.jms.endpoints.DefaultConsumerMarshaler"> > <property name="mep" value="http://www.w3.org/2004/08/wsdl/in-out"; /> > </bean> > > On Wed, Mar 26, 2008 at 12:26 AM, patmcg <[EMAIL PROTECTED]> wrote: > >> >> Hi, >> >> I'm trying to mask a request/response JMS service behind an HTTP Web >> Service. I have this working with the "old" JMS endpoints. However my >> understanding is that the "new" JMS endpoints are InOnly. Does that mean >> I >> can not implement this type of feature using the "new" JMS endpoints? >> >> If it really is possible, is there a recommended way to do this? If its >> not >> possible, then I would suggest updating the documentation to notify the >> users of this shortcoming. >> -- >> View this message in context: >> http://www.nabble.com/HTTP-In-Out-SU-connection-to-new-JMS-Endpoint-tp16291331s12049p16291331.html >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > > -- View this message in context: http://www.nabble.com/HTTP-In-Out-SU-connection-to-new-JMS-Endpoint-tp16291331s12049p16295029.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
