-
1. Re: Trouble with cxfbc to Camel route
ffang Jul 19, 2010 8:54 PM (in response to klimperos)Hi,
The from uri in your camel route should be
jbi:endpoint:serviceNamespace[sep]serviceName[sep]endpointName[?options]
here the serviceNamespace should be http://poc.test.com/POC/ but not the prefix poc.
Freeman
-
2. Re: Trouble with cxfbc to Camel route
njiang Jul 19, 2010 8:55 PM (in response to klimperos)Hi
Your cxfbc target service has the namespace prefix definition.
Please use this uri for your camel jbi endpoint to receive the request from cxfbc.
"jbi:endpoint:http://poc.test.com/POC/wtservice/wtendpoint"
Then you can send the response back after the file endpoint from the camel route.
Willem
-
3. Re: Trouble with cxfbc to Camel route
klimperos Jul 19, 2010 10:32 PM (in response to ffang)Freeman, Willem,
It turned out that since my poc namespace is "http://poc.test.com/POC/" that a second '/' is required after POC to form the uri correctly to match:
Curiously, while I don't explicitly send any reply back to cxfbc, my test client received a reply with a copy of the input message. Any thoughts as to why this occurs? Also, why doesn't the above uri require an explicit mep=in-out since cxfbc is expecting a reply?
Thank you - I appreciate your help.
Kevin
-
4. Re: Trouble with cxfbc to Camel route
ffang Jul 19, 2010 10:38 PM (in response to klimperos)Hi,
Cxf bc will create Message Exchange Pattern(InOnly or InOut) based on the servicemodel(which is generated from the wsdl you specified for cxf bc consumer) automatically, so you needn't specify the MEP yourself, all is based on the wsdl.
Freeman
-
5. Re: Trouble with cxfbc to Camel route
njiang Jul 20, 2010 3:08 AM (in response to klimperos)Camel pipeline processor will copy the in message from the last exchange back to the first exchange out message, if the last exchange doesn't have the out message.
So it is not strange to see the request message return, as I said you need to put the response message back by using the setOutBody() or processor() DSL.
Willem