Action-169 Apply resolutions for Issues 35-37

For master test index see:

http://dev.w3.org/2008/ws/soapjms/testcases/testcases/testcases.html

Note 2 new tests for basic SOAP 1.2 functionality - one-way and two-way respectively:

http://dev.w3.org/2008/ws/soapjms/testcases/testcases/testcases.html#test0101
http://dev.w3.org/2008/ws/soapjms/testcases/testcases/testcases.html#test0102

These 2 tests have changed:

http://dev.w3.org/2008/ws/soapjms/testcases/testcases/testcases.html#test1003
http://dev.w3.org/2008/ws/soapjms/testcases/testcases/testcases.html#test1103

The test cases verify :

http://www.w3.org/TR/soapjms/#Protocol-2012

(Charset must match the encoding value from the supplied XML ... Fault subcode contentTypeMismatch)

The message from A to B have a charset that mismatches the XML declaration (UTF-8).

The stale reference to 2013 has been removed.

Before
jmsmsg:SOAPJMS_contentType = 'text/plain'

After:
jmsmsg:SOAPJMS_contentType = 'text/xml; charset=UTF-16'




These tests have been corrected to reflect delivery mode of persistent(2):

http://dev.w3.org/2008/ws/soapjms/testcases/testcases/testcases.html#test0013
http://dev.w3.org/2008/ws/soapjms/testcases/testcases/testcases.html#test0014
http://dev.w3.org/2008/ws/soapjms/testcases/testcases/testcases.html#test0015
http://dev.w3.org/2008/ws/soapjms/testcases/testcases/testcases.html#test0016