On 03/17/2011 10:46 PM, Edumudi Viswanath wrote:
...
1. Reliable messaging assures that messages sent from RM source(client) will
reach to RM Destination(server) and vice versa. Right??
Yes to the first part, maybe to the second. The client has the option of
allowing the server to offer a return sequence, used for response
messages sent from the server to the client. Normally the server should
offer the return sequence if the client allows it, but I suppose there
are situations where you wouldn't want to.
2. Reliable messaging mechanism comes into picture only when RM-Source(client)
sending messages to RM-Destination(server) for processing& while sending
response back to client(RM Destination) from server(RM Source) and It has no role,
if in case db is down due to some reason or processing of request can't be done due
to some issue. Is it right??
The RM Destination is not supposed to acknowledge a message until it has
been delivered to the application code at that end. What happens after
that is up to the application. If the service provider is unable to
function, I'd expect it to return a Fault.
3. We can test an application which implements ws-rm even from a client which
doesn't implement ws-rm (for example: soapUI tool). Right?
As long as the server policy makes WS-RM optional I'd think this should
work. If WS-RM is required, the server should reject any attempts to
communicate without using it.
- Dennis
