ISSUE-36 (Test cases with incorrect assertion references): soap-jms test-cases 1003 and 1103 should be reviewed perhaps have assertion references changed [SOAP-JMS Test cases]

ISSUE-36 (Test cases with incorrect assertion references): soap-jms test-cases 1003 and 1103 should be reviewed perhaps have assertion references changed [SOAP-JMS Test cases]

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

Raised by: Eric Johnson
On product: SOAP-JMS Test cases

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

1103 references Assertion Protocol-2013 which is now eliminated. 1003 and 1103 reference Assertion Protocol-2012 which is about charset checking:

Protocol-2012:  (contentType) if the charset parameter is specified it is checked to ensure that it matches the encoding value from the supplied XML. If there is a mismatch then a fault MUST be generated.

However, both tests have text/plain in the SOAPJMS_contentType. It seems therefore that Protocol-2015 is being tested:

Protocol-2015: the contentType parameter MUST reflect the value specified in the Content-type part header for the first part (the SOAP body, so text/xml or application/xop+xml).