W3C home > Mailing lists > Public > public-soap-jms@w3.org > July 2010

Applied changes for ACTION-185

From: Mark Phillips <M8PHILLI@uk.ibm.com>
Date: Tue, 6 Jul 2010 13:09:28 +0100
To: public-soap-jms@w3.org
Message-ID: <OFFE6E8037.019B451E-ON80257758.003844BE-80257758.0042C8E3@uk.ibm.com>

I have made the following changes in response to action 185 - "Change the
namespace to http://www.w3.org/2010/soapjms"


Old namespace:   "http://www.w3.org/2008/07/soap/bindings/JMS/"
New namespace "http://www.w3.org/2010/soapjms"


Binding Specification:
===================
The old namespace was referenced in the following sections of the Binding
specification.  These have been updated to use the new namespace:

1.4.1 XML Namespaces (in table and text)
1.6 Conformance (bullets 1,2, and 3)
2 The SOAP/JMS Underlying Protocol Binding (in second sentence)
2.8 Faults (in SOAP 1.2 and SOAP 1.1 example)
3.4 WSDL 1.1 Extensions Detail (in second sentence)
3.4.1 Example (in binding and transport of WSDL 1.1 example)
3.4.2 WSDL 1.1 Transport Identification (end of first paragraph and in
example)
3.5 WSDL 2.0 Extensions Detail (in second sentence, twice in the example,
and once in the text following example)
Appendix B (twice in schema)

Before:
http://dev.w3.org/cvsweb/2008/ws/soapjms/soapjms.html?rev=1.85&content-type=text/html;
 charset=utf-8
After:
http://dev.w3.org/cvsweb/2008/ws/soapjms/soapjms.html?rev=1.86&content-type=text/html;
 charset=utf-8

TestCases
=========
The old namespace was referenced as the soap transport in WSDL fragments in
a number of testcases.  These testcases have been updated to use the new
namespace.

test0006
test0007
test0013
test0014
test0015
test0016

Before:
http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/testcases/testcases/testcases.html?rev=1.22&content-type=text/html;%20charset=iso-8859-1
After:
http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/testcases/testcases/testcases.html?rev=1.23&content-type=text/html;%20charset=iso-8859-1



Test Messages.
==============
The old namespace was referenced as the faultcode namespace in a number of
test messages.  These messages have been updated to use the new namespace.

CVS Log:
http://dev.w3.org/cvsweb/2008/ws/soapjms/testcases/documents/messages/?f=h

soap1.1:
= = = = =
http://dev.w3.org/cvsweb/2008/ws/soapjms/testcases/documents/messages/soap11/?f=h

contentTypeMismatchFault.xml
malformedRequestURIFault.xml
mismatchedSoapActionFault.xml
missingContentTypeFault.xml
missingRequestURIFault.xml
targetServiceNotAllowedInRequestURIFault.xml
unrecognizedBindingVersionFault.xml
unsupportedJMSMessageFormatFault.xml

soap 1.2
= = = = =
http://dev.w3.org/cvsweb/2008/ws/soapjms/testcases/documents/messages/soap12/?f=h

contentTypeMismatchFault.xml
malformedRequestURIFault.xml
mismatchedSoapActionFault.xml
missingContentTypeFault.xml
missingRequestURIFault.xml
targetServiceNotAllowedInRequestURIFault.xml
unrecognizedBindingVersionFault.xml
unsupportedJMSMessageFormatFault.xml


FaultCases
==============
http://dev.w3.org/cvsweb/2008/ws/soapjms/testcases/faultcases/?f=h

contentTypeMismatchStyle.xml
malformedRequestURIStyle.xml
mismatchedSoapActionStyle.xml
missingContentTypeStyle.xml
missingRequestURIStyle.xml
targetServiceNotAllowedInRequestURIStyle.xml
unrecognizedBindingVersionStyle.xml
unstyledSOAP12Fault.xml
unsupportedJMSMessageFormatStyle.xml


This completes action 185.

Regards
Mark
Received on Tuesday, 6 July 2010 12:19:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:16:24 GMT