2010-05-17 23:57:26: Created issue 'soap-jms test-cases 1003 and 1103 should be reviewed perhaps have assertion references changed' nickname Test cases with incorrect assertion references owned by Eric Johnson on product SOAP-JMS Test cases, description 'From email:
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).
' non-public [Eric Johnson]