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

ISSUE-8 (Incorrect example, section C2): Example in C2 contrary to Protocol-2029 [SOAP-JMS Binding specification]

From: SOAP-JMS Binding Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Wed, 29 Jul 2009 20:25:27 +0000 (GMT)
To: public-soap-jms@w3.org
Message-Id: <20090729202527.D7FCA6B646@tibor.w3.org>

ISSUE-8 (Incorrect example, section C2): Example in C2 contrary to Protocol-2029 [SOAP-JMS Binding specification]

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

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

Description:
------------

in the example, the text of the example starts with this:

MIME-Version: 1.0

Content-Type: Multipart/Related;boundary=MIME_boundary;
    type="application/xop+xml";
    start="<945414389.1092086011970>";
    startinfo="application/soap+xml"

This, of course, is contrary to Protocol-2029, which reads:

Note also that if the payload is formatted as a MIME multipart message, then the first byte or character encountered in the JMS Message body MUST be the start of the MIME boundary for the start of the first part — what MIME Part One [IETF RFC 2045] section 2.5 calls a "Body Part".

Justification:
--------------

Example should match the normative text

Proposal:
---------
Remove all the text in the example that comes before the first MIME boundary.

(Note that this is a formal filing of an issue from the email http://lists.w3.org/Archives/Public/public-soap-jms/2009Jul/0001.html )

-Eric Johnson
Received on Wednesday, 29 July 2009 20:33:39 GMT

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