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

Fw: ACTION-70: rewording Content-type discussion

From: Phil Adams <phil_adams@us.ibm.com>
Date: Tue, 10 Mar 2009 11:56:41 -0500
To: public-soap-jms@w3.org
Message-ID: <OFFA771204.E4DFFE24-ON86257575.005C8746-86257575.005D14E3@us.ibm.com>
This is my final answer :)

The contents of the JMS Message body MUST be the SOAP payload as a JMS 
BytesMessage or TextMessage.[Definition: Use fault subcode 
unsupportedJMSMessageFormat when the arriving message format is not 
BytesMessage or TextMessage. †]. The formatting of the SOAP payload is 
determined by the SOAP node, and should follow the same rules as for the 
SOAP/HTTP 
binding, as described in the following specifications:  SOAP 1.1 
specification, 
SOAP 1.2 specification, RFC 2376, RFC 2045.
The primary requirement is that the value used for the Content-type 
MUST be consistent with the formatting of the SOAP payload.   For example, 
if the 
SOAP payload is formatted as a simple SOAP envelope, the Content-type 
value MUST be specified as "text/xml" for SOAP 1.1 or 
"application/soap+xml" for SOAP 1.2.  On the other hand, if the SOAP 
payload is formatted as a MIME multipart message, the Content-type 
value MUST be specified as "multipart/related".   In this way, the 
SOAP node determines the proper formatting of the SOAP payload 
irrespective of the underlying JMS message, and specifies a corresponding 
value for the Content-type which appropriately describes it to 
the receiving SOAP node.  Note also that if the payload is formatted as a 
MIME multipart message, then the first thing encountered in the JMS 
Message 
Body's byte stream MUST be the MIME boundary for the start of the first 
part — 
what MIME Part One [IETF RFC 2045] section 2.5 
calls a "Body Part". The message will be encoded using SOAP Messages with 
Attachments [SOAP Messages with Attachments] 
or XOP [SOAP 1.1 Binding for MTOM 1.0] [SOAP MTOM], in either case with a 
Content-type value of "multipart/related".

Let me know if this passes muster...

Thanks,
Phil 
__________________________________________________________________________________________________________ 

Phil Adams
phil_adams@us.ibm.com
WebSphere Application Server
Office: (512) 286-5041 (t/l 363)
Web Services Development
Mobile: (512) 750-6599
IBM - Austin, TX


----- Forwarded by Phil Adams/Austin/IBM on 03/10/2009 11:50 AM -----

From:
Phil Adams/Austin/IBM@IBMUS
To:
public-soap-jms@w3.org
Date:
03/10/2009 11:43 AM
Subject:
ACTION-70: rewording Content-type discussion
Sent by:
public-soap-jms-request@w3.org




Sorry, my original email had an incorrect action # in the subject... 

Phil 
__________________________________________________________________________________________________________ 

Phil Adams 
phil_adams@us.ibm.com 
WebSphere Application Server 
Office: (512) 286-5041 (t/l 363) 
Web Services Development 
Mobile: (512) 750-6599 
IBM - Austin, TX 



----- Forwarded by Phil Adams/Austin/IBM on 03/10/2009 11:40 AM ----- 
From: 
Phil Adams/Austin/IBM 
To: 
public-soap-jms@w3.org 
Date: 
03/10/2009 11:39 AM 
Subject: 
ACTION-77: rewording Content-type discussion



Latest proposal for the wording of section 2.4 of the binding spec with 
respect to Content-type: 

The contents of the JMS Message body MUST be the SOAP payload as a JMS 
BytesMessage or TextMessage.[Definition: Use fault subcode 
unsupportedJMSMessageFormat when the arriving message format is not 
BytesMessage or TextMessage. †]. The formatting of the SOAP payload is 
determined by the SOAP node, and should follow the same rules as for the 
SOAP/HTTP 
binding, as described in the following specifications:  SOAP 1.1 
specification, 
SOAP 1.2 specification, RFC 2376, RFC 2045.
The primary requirement is that the value used for the Content-type 
property must be 
consistent with the formatting of the SOAP payload.   For example, if the 
SOAP payload is formatted as a simple SOAP envelope, the Content-type 
value must be specified as "text/xml" for SOAP 1.1 or 
"application/soap+xml" for SOAP 1.2.  On the other hand, if the SOAP 
payload is formatted as a MIME multipart message, the Content-type 
must be specified as "multipart/related".   In this way, the 
SOAP node determines the proper formatting of the SOAP payload 
irrespective of the underlying JMS message, and specifies a corresponding 
value for the Content-type value which appropriately describes it to 
the receiving SOAP node.  Note also that if the payload is formatted as a 
MIME multipart message, then the first thing encountered in the JMS 
Message 
Body's  byte stream MUST be the MIME boundary for the start of the first 
part — 
what MIME Part One [IETF RFC 2045] section 2.5 
calls a "Body Part". The message will be encoded using SOAP Messages with 
Attachments [SOAP Messages with Attachments] 
or XOP [SOAP 1.1 Binding for MTOM 1.0] [SOAP MTOM], in either case with a 
Content-type of "multipart/related".


Comments?


Phil 
__________________________________________________________________________________________________________ 

Phil Adams 
phil_adams@us.ibm.com 
WebSphere Application Server 
Office: (512) 286-5041 (t/l 363) 
Web Services Development 
Mobile: (512) 750-6599 
IBM - Austin, TX 




Received on Tuesday, 10 March 2009 16:57:28 GMT

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