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

Test cases with incorrect assertion references

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

State:

CLOSED

Product:

SOAP-JMS Test cases

Raised by:

Eric Johnson

Opened on:

2010-05-17

Description:

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

Related Actions Items:

No related actions

Related emails:

1. Agenda for the 2010-05-25 conference call (from eric@tibco.com on 2010-05-24)
2. Agenda for the 2010-05-18 conference call (from eric@tibco.com on 2010-05-17)
3. 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] (from sysbot+tracker@w3.org on 2010-05-17)

Related notes:

Display change log