On 2011-1-25, at 上午4:28, HART wrote:
Hi Geert,
Thanks for the reply!
The CXFSE is actually executing some processes triggered by
something else,
so for the scenario we are talking about here, it is the client
component
that sends out a request to the external WS.
You are right about the "bad" messages. I only described the basics
of the
scenario. We will add email alerts and max count of retries to
prevent it
from corrupting the queues and processes.
Where should I capture the exception? Using cxf interceptor?
You can get the exception or a fault response message in cxf se
endpoint, it depend on how your cxf se endpoint send out request to
jms provider.
If cxf se use proxy, then you can get exception directly, if cxf se
use NMR client api, then it should be able to get fault response which
indicate something wrong.
Freeman
Thanks,
Hart
--
View this message in context:
http://servicemix.396122.n5.nabble.com/Capture-network-communication-problem-tp3346353p3355232.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
