Hello Sandesha-istas! I was working on some interop testing between Sandesha 1.0 and WebLogic Server 9.2 in which a Sandesha 1.0 client engages in a request-response exchange with a WLS 9.2 server. Everything works fine up until the point that the client calls SandeshaContext.endSequence(). At this point the client has terminated the outbound sequence via a wsrm:TerminateSequence message but the inbound sequence (established via an offer during the initial CreateSequence/CreateSequenceResponse handshake) is still active. The Sandesha 1.0 client blocks in endSequence() until the inactivity timeout for that sequence is reached and an exception is thrown.
Although I can understand that there may be reasons that the client would want to block until the offered sequence is terminated, I don't think it is reasonable to expect that terminating an outbound sequence will necessarily result in the server automatically terminating the inbound sequence. I couldn't find any language in the 200502 specs that mandates such a linkage between the inbound and outbound sequences. I think the application should be allowed to select from three possible behaviors for endSequence(): 1) block waiting for all active inbound sequences to be terminated (current behavior) 2) send a SequenceTerminated fault to all active inbound sequences 3) simply clean up the sequence What do people think? -- Gilbert Pilz Sr. Principal Technologist Office of the CTO BEA Systems, Inc. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
