Request/Reply pattern without jms?

[santhosh <ra...@gmail.com>]

 0 down vote favorite
	

My requirement is to have a web service which will receive the request from
clients and then route through camel,enrich it and forward it to another
webservice at other clients place ,get response and send it back to the
original requestor.

from(webserviceURI)
  .inOut().to("jms:queue:INQueue?replyTo=OUTQueue?replyToType=Exclusive");

from(jms:queue:INQueue).to("http:X").to(jms:OUTQueue)

I am understanding correct.Do we need to set ReplyTo header if we do this. I
guess this solves the problem .Earlier in a post at stackExchange
(http://stackoverflow.com/questions/10253656/how-to-connect-an-apache-camel-synchronous-request-reply-endpoint-with-asynchron),
Claus  had explained there is no need to set correlation id as camel does it
automatically if it isnt assigned.

My questions are we are looking ultra light weight implementation.we might
have to contend with memory as low as 300 MB.No activeMQ,no SMX.Just going
with karaf.what is the best jms provider if we need to use jms that has
small footprint.or is activemq ok.

I also thinking of doing this

<from uri="cxf:bean:cxfProxyEndpoint?dataFormat=MESSAGE" />
<camel:convertBodyTo type="java.lang.String"></camel:convertBodyTo>

<to uri="http://X:8080/X">


The cxf proxy webservice has operations that returns a value.So we receive
the request ,send it to preprocessors and then call remote webservice as
http endpoint ,get the response ,post process it and the response is message
at end of route(am i correct).My question would the request and response
match.How should i test it.we also will be multicasting the request from
proxy to various http endpoints and aggregating the replies before sending
it out to client requestor.Should i really proceed in this route or is it a
poor design.




--
View this message in context: http://camel.465427.n5.nabble.com/Request-Reply-pattern-without-jms-tp5723754.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Request/Reply pattern without jms?

[Claus Ibsen <cl...@gmail.com>]

Hi

This questions has been posed first at StackOverFlow
http://stackoverflow.com/questions/13758380/apache-camel-request-reply-without-activemq-jms



On Fri, Dec 7, 2012 at 9:20 AM, santhosh <ra...@gmail.com> wrote:
>  0 down vote favorite
>
>
> My requirement is to have a web service which will receive the request from
> clients and then route through camel,enrich it and forward it to another
> webservice at other clients place ,get response and send it back to the
> original requestor.
>
> from(webserviceURI)
>   .inOut().to("jms:queue:INQueue?replyTo=OUTQueue?replyToType=Exclusive");
>
> from(jms:queue:INQueue).to("http:X").to(jms:OUTQueue)
>
> I am understanding correct.Do we need to set ReplyTo header if we do this. I
> guess this solves the problem .Earlier in a post at stackExchange
> (http://stackoverflow.com/questions/10253656/how-to-connect-an-apache-camel-synchronous-request-reply-endpoint-with-asynchron),
> Claus  had explained there is no need to set correlation id as camel does it
> automatically if it isnt assigned.
>
> My questions are we are looking ultra light weight implementation.we might
> have to contend with memory as low as 300 MB.No activeMQ,no SMX.Just going
> with karaf.what is the best jms provider if we need to use jms that has
> small footprint.or is activemq ok.
>
> I also thinking of doing this
>
> <from uri="cxf:bean:cxfProxyEndpoint?dataFormat=MESSAGE" />
> <camel:convertBodyTo type="java.lang.String"></camel:convertBodyTo>
>
> <to uri="http://X:8080/X">
>
>
> The cxf proxy webservice has operations that returns a value.So we receive
> the request ,send it to preprocessors and then call remote webservice as
> http endpoint ,get the response ,post process it and the response is message
> at end of route(am i correct).My question would the request and response
> match.How should i test it.we also will be multicasting the request from
> proxy to various http endpoints and aggregating the replies before sending
> it out to client requestor.Should i really proceed in this route or is it a
> poor design.
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Request-Reply-pattern-without-jms-tp5723754.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen