Request To Raise Issue: soap-jms test-cases 1003 and 1103 should be reviewed perhaps assertion references changed

• From: Peter Easton <peaston@progress.com>
• Date: Mon, 17 May 2010 16:03:05 -0400
• To: "public-soap-jms@w3.org" <public-soap-jms@w3.org>
• Message-ID: <6F07B1E4CA74F3469AAA1DA148515F8401463041B7@PSCMAIL02.bedford.progress.com>

Title: soap-jms test-cases 1003 and 1103 should be reviewed perhaps have assertion references changed

Description: 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).

Received on Monday, 17 May 2010 20:04:12 UTC