DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15683>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15683 Unusual contract between JMS service and WSIF Summary: Unusual contract between JMS service and WSIF Product: Axis-WSIF Version: current (nightly) Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Basic Architecture AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When communicating with a JMS service through a request-response operation, WSIF sends the request to the service as a JMS message, recording the JMS message ID. WSIF then listens on a temporary queue for a response whose JMS correlationID field is required to match the message ID of the request message. This seems like an unusual contract, it would make more sense to use one of the fields (the JMSMessageID or the JMSCorrelationID) in both cases.
