Hi Hart,
In theory, oneway(InOnly MEP) means there's no any response(including
the fault response) you care about. If it's oneway invocation, cxfbc
provider also just send out request and don't care how the request is
going on.
You may need refactor your working flow, as you want to catch fault
somewhere, you can't use oneway(InOnly MEP).
Freeman
On 2011-1-27, at 上午11:15, HART wrote:
Hi Freeman,
Unfortunately, it is an asynchronous request, and it has to be one-
way.
That's why I do not have anything that can wait for a response. The
response
will come back later through a separate channel. The only component
that may
know about the communication problem is the cxfbc provider which
sends the
request out (or the camel-cxf).
So I wonder maybe someone already encountered similar situation...
It sounds
like a typical scenario.
Thanks,
Hart
--
View this message in context:
http://servicemix.396122.n5.nabble.com/Capture-network-communication-problem-tp3346353p3359174.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
--
Freeman Fang
------------------------
FuseSource: http://fusesource.com
blog: http://freemanfang.blogspot.com
twitter: http://twitter.com/freemanfang
Apache Servicemix:http://servicemix.apache.org
Apache Cxf: http://cxf.apache.org
Apache Karaf: http://karaf.apache.org
Apache Felix: http://felix.apache.org