Hart, Is my assumption correct that you aren't running an actual webservice implementation, but want to create a caching proxy for an external webservice?
In that case you will need 2 CXF BindingComponent endpoints, and no ServiceEngine endpoints. Secondly, your strategy of storing requests in a queue and retrying them until success is achieved is quite dangerous, because the average request has a certain expiration date after which the request becomes useless or even dangerous. (You could end up executing a request that was send 2 hours ago, while the sending party in the mean while has worked around the non responsive webservice. The old request then could corrupt the dataset). Kind regards, Geert. > > Hi Freeman, > > Thanks a lot for your detailed explanation! > > The message flow we are planning to use is this: > > cxfse (send request, acting as client proxy for an external WS) --> JMS > Provider --> QueueA --> JMS Consumer --> cxfbc provider --> external WS > service --> if failed put the request into QueueB with timer --> request > is > put back to QueueA to process > > The keys to this design are: > 1. make the process asynchronous by using queues > 2. re-try the request until it succeeds > > I am fairly new to SMX, so I am not sure whether the above process makes > any > sense to you, and if not, what would be a better approach? If the design > does not have any problem, where and how we can catch the communication > error? > > Best regards, > Hart > -- > View this message in context: > http://servicemix.396122.n5.nabble.com/Capture-network-communication-problem-tp3346353p3353823.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. > > >
