One of my colleagues points out a mistake in our CR, section C.2. Specifically, 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". -Eric.Received on Wednesday, 1 July 2009 19:56:11 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 1 July 2009 19:56:11 GMT