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

Updated proposal for ISSUE-65, complete ACTION-232

From: Eric Johnson <eric@tibco.com>
Date: Mon, 06 Dec 2010 12:06:26 -0800
Message-ID: <4CFD4242.1030306@tibco.com>
To: SOAP-JMS <public-soap-jms@w3.org>
Completing my ACTION-232, updating this proposal with two changes:

  * Add the fault to the schema section.
  * Add an explicit bullet that the contentEncoding is not supported for 
multipart messages, as per text from Amy.

===> Add to section 2.2.3:

[Definition: soapjms:contentEncoding] (xsd:string)
   * Identifies the transformation that has been applied to the message 
payload body.  Contains one of the values defined by IANA for the 
Content-Coding values of [IANA HTTP PARAMS].  Defaults to "identity" if 
the property is not present.
   * Corresponds to the JMS Message property named SOAPJMS_contentEncoding
   * [Definition: If the content encoding is specified, it is checked to 
ensure that it matches the content encoding values supported. A fault 
MUST be generated with subcode contentEncodingNotSupported if the 
encoding values do not match.]
   * Restriction: the meaning of the property is not defined for 
composite messages (messages with a Content-Type of "multipart" or 
"message"), only for discrete messages (Content-Type "application" or 
"text", for this specification).

===> Change to section 2.4:

Replace "The bytes or characters of the JMS Message payload correspond 
to the MIME format as indicated by the definition of the contentType 
property" with:

"After being decoded according to the contentEncoding property, the 
bytes or characters of the JMS Message payload correspond to the MIME 
format as indicated by the definition of the contentType property"

===> Addition to section 2.4.1

New bullet point:
  * Use of the contentEncoding property is not defined, since the 
underlying message payload is not raw bytes.

===> Add to section 2.8

Add an entry for contentEncodingNotSupported to the list in this section.

===> Add to section A.1 (Normative References)

[IANA HTTP PARAMS]
   Hypertext Transfer Protocol (HTTP) Parameters, Internet Assigned 
Names And Numbers (IANA), Sept. 2, 2009, Available at 
http://www.iana.org/assignments/http-parameters/http-parameters.xml

==== Add to Appendix B:

In the definition of FaultCodesType, add:

       <xs:enumeration value="soapjms:contentEncodingNotSupported"/>

===== ******* =====

-Eric.
Received on Monday, 6 December 2010 20:07:18 GMT

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