Hi, I am trying out the ws-rm demo sample includced in cxf-2.2.7 (demo.ws_rm.client.Clinet) and I am confused with the behavior of this client as well as what I see in the RM interceptors..
It is working fine as long as the server is available. But I am confused with its behavior when the server is unavailable or some transmission error occurs. >From my experience with sandesha2 and its simple demo examples, I thought the cxf's ws-rm demo client would try to retransmit the message (I mean, the RM runtime would take care of the retransmission) when there is some transmission error. However, what I observed is that this client doesn't try to retransmit the message at all when the server is unavailable prior to the createSequence step. If the server is available at the createSequence step but becomes unavailable before the application message transmission, the retransmission of this application message is performed by another thread, but the original client thread is getting the ConnectException and this is not what I expected. I expected that the RM runtime to handle the exception and return just the control back the client without throwing any exception. If the client gets the exception, I don't see any use of this mechanism. So I hope I am doing something wrong and someone can tell me how to make the RM runtime work like I am expecting. Thanks. Regards, aki
