On Mon, Feb 10, 2014 at 8:29 AM, Mandy Warren <mandys.in...@gmail.com> wrote: > Thanks Jason, we did consider this but it still involves creating additional > threads and hence making it tricky to debug. We are really after a solution > which allows a synchronous call across (same jvm) wars on a single thread. >
That is what direct-vm can do. Though you need to have camel-core on a shared classpath. > Many thanks > Mandy > > Sent from a mobile device > >> On 9 Feb 2014, at 23:32, Jason Dwyer <jason.dw...@gmail.com> wrote: >> >> hi there, >> >> i'm fairly new to camel too, so defer to other answers as they come along, >> >> but have you considered using an activemq ( or other jms ) broker ? >> >> its pretty painless to set one up, and expose the tcp transport. instead of >> sending to direct or direct-vm, send to a queue, then have a second route >> consume it. >> >> ( you might even find deploying a third war with just activemq keeps it >> nice and decoupled ) >> >> i've been pushing little blobs ( <1k ) of json onto a queue then reading >> off with multiple consumers and can get many thousands per second through >> on a not too beefy laptop . >> >> hope this helps >> >> cheers >> >> j >> >> >> >> >>> On 10 February 2014 09:21, Mandy Warren <mandys.in...@gmail.com> wrote: >>> >>> Hi, >>> >>> I've just started looking at Camel and I was wondering whether there was a >>> way to call from a CXF rest service deployed in war A to a CXF rest service >>> deployed in war B without the overhead of an HTTP call if both wars are >>> deployed in the same JVM? >>> >>> Some background to my requirement.. >>> - we have a large number of cxf services deployed in weblogic and a single >>> service may call 2 or 3 other services to complete its work. We'd ideally >>> like the calls to be made on a single thread when the calls are within the >>> same JVM as it makes debugging much easier. >>> >>> Local transport in CXF looks ideal except it doesn't work across wars (at >>> least I haven't managed to make it work). >>> >>> direct-vm looks interesting but I don't want the 2 services to be dependent >>> on each others service interface classes - instead I'd just like to pass a >>> JSON request between the 2 services and then have something execute the >>> appropriate rest service (and it's interceptors ideally). >>> >>> Is there any way to achieve this? >>> >>> Many thanks >>> Mandy >>> -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen Make your Camel applications look hawt, try: http://hawt.io
