Re: Camel Resequencer and JMs transactions

2015-05-10 Thread amit2103
Many thanks for the answer, Claus. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Resequencer-and-JMs-transactions-tp5766843p5766917.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: QueueReplyManager - reply received for unknown correlationID

2015-05-10 Thread Henrique Viecili
Is there any documentation about uncorrelated messages sent to reply destinations? How does it behave when the reply destination is shared/exclusive/temporary? Regards, Henrique Viecili Henrique Viecili On 9 May 2015 at 16:54, Claus Ibsen wrote: > Hi > > What Camel and AMQ version do you use?

Re: QueueReplyManager - reply received for unknown correlationID

2015-05-10 Thread Willem Jiang
The CorrelationID is quite important when the message exchange pattern is InOut.  What’s the transport that you use in CXF endpoint? If it uses the JMS transport, I guess that could cause some trouble in your route. Regards, -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http

Re: Unmarshal not working

2015-05-10 Thread Willem Jiang
Please use the PAYLOAD data format, as the Message data format just redirect the underlay Stream for you in camel route, if you don’t want to handle the SOAP envelope yourself, PAYLOAD is your first choice. -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blog

Re: camel-context.xml getting loaded multiple times

2015-05-10 Thread Willem Jiang
If you don’t want to common camel-context be load multiple times, you can just deploy it in a single war. If you just want to reuse the route definition, you can take a look this FAQ[1] using the routeContext to do that kind of job. [1]http://camel.apache.org/how-do-i-import-routes-from-other-xm

Re: Using quartz and quartz2

2015-05-10 Thread Willem Jiang
Hi, You are not supposed to use tow quartz endpoint with same relative path setting. Please change the uri to another path such as "quartz://sync/myTimer2”. -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) T

Re: Vramel or modifying Camel

2015-05-10 Thread Willem Jiang
You can integrate the vert.x with Camel by implement the camel component API (which could be a more easy way to go), and we just have camel-vertx component[1] to do this kind of work. the Vramel way is like reimplement the Camel DSL on base of vert.x API, which need to lots of work to reimpleme

Handle Soap1.1 and Soap1.2 payloads in a single CXF WS Endpoint

2015-05-10 Thread Gnanaguru S
Hi All Camel cxf users, A general question on how to handle both Soap 1.1 and Soap1.2 payloads in a single CXF gateway endpoint ( with cxf dataformat is MESSAGE) I am exposing my camel routes through a WS endpoint, my cxf endpoint definition looks as shown below: http://www.test.com

Re: Unmarshal not working

2015-05-10 Thread jainmcs03
But my real webservice doesnt support PAYLOAD format thats why chose MESSAGE format. So just need to remove the soap envelope and do unmarshal. Any guide pls? -- View this message in context: http://camel.465427.n5.nabble.com/Unmarshal-not-working-tp5766790p5766948.html Sent from the Camel - Us

Re: Transformation PAYLOAD request

2015-05-10 Thread jainmcs03
Thanks, Claus. Actually im trying canonical service proxy so after the unmarshall need to get the request value from been object and set it into different object for transformation. For that any example pls share the link. I searched more but no clue. Regards Jayendran -- View this message i

Re: Transformation PAYLOAD request

2015-05-10 Thread jainmcs03
Below is the actual route. .. .. For Ex. How to get MemberInfo(localhost._8080.canonicalcxfserviceproxy.canonical.MemberInfo) in ReqTransformationProcessor class. Regards Jayendran -- View this message in context: htt

Re: Transformation PAYLOAD request

2015-05-10 Thread jainmcs03
I managed to get the value. Thanks, Inside ReqTransformationProcessor : InquiryRequestType : localhost._8080.canonicalcxfserviceproxy.canonical.InquiryRequestType@5ec7baab Inside ReqTransformationProcessor : RequestBodyType : localhost._8080.canonicalcxfserviceproxy.canonical.RequestBodyType@ab061