W3C home > Mailing lists > Public > public-soap-jms@w3.org > July 2010

ISSUE-51 (redundant assertions about message body): Protocol 2034 & 2040 are redundant normative statements about the message body format [SOAP-JMS Binding specification]

From: SOAP-JMS Binding Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Fri, 16 Jul 2010 18:31:03 +0000
To: public-soap-jms@w3.org
Message-Id: <E1OZpgd-0006jl-Q7@stu.w3.org>

ISSUE-51 (redundant assertions about message body): Protocol 2034 & 2040 are redundant normative statements about the message body format [SOAP-JMS Binding specification]

http://www.w3.org/2002/ws/soapjms/tracker/issues/51

Raised by: Eric Johnson
On product: SOAP-JMS Binding specification

>From email: http://lists.w3.org/Archives/Public/public-soap-jms/2010Jul/0013.html

Description:
Protocol 2027: "The contents of the JMS Message body MUST be the SOAP
payload as a JMS BytesMessage or TextMessage. "

Protocol 2034: "(request-response MEP - requesting node) The message
MUST  be created as a JMS BytesMessage or TextMessage as defined in 2.4
The JMS Message Body."

Protocol 2040: The message MUST be created as a JMS BytesMessage or
TextMessage  as defined in 2.4 The JMS Message Body.†

I conclude that normative statements 2034, 2040 are redundant with 2027.

Proposal:

Change 2034 to (no longer a normative assertion):
 "The message is created as a JMS BytesMessage or TextMessage as defined in 2.4 The JMS Message Body."

Change 2040 to (no longer a normative assertion):
"The message is created as a JMS BytesMessage or TextMessage as defined in 2.4 The JMS Message Body."
Received on Friday, 16 July 2010 18:31:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:16:24 GMT