- From: Mark Phillips <M8PHILLI@uk.ibm.com>
- Date: Tue, 28 Jul 2009 16:56:54 +0100
- To: public-soap-jms@w3.org
In response to Action 94 [1], I propose that we delete the Protocol-2024
assertion, and change the requestURI property description in section 2.2.3
[2] to:
* * *
Specifies the JMS URI of the service. The client MUST create this by taking
the supplied URI, leaving the destinationName as-is, and removing the
targetService and replyToName query parameters if they are specified. The
client SHOULD also remove deliveryMode, jndiConnectionFactoryName,
jndiInitialContextFactory, jndiURL, jndiContextParameter, timeToLive,
priority properties, and MAY remove other query parameters not explicitly
mentioned above (for example client security related properties).
The client MUST create the requestURI property using the above rules.
[Protocol-2021]
* * *
[1] http://www.w3.org/2002/ws/soapjms/tracker/actions/94
[2] http://www.w3.org/TR/2009/CR-soapjms-20090604/#binding-message-props
Mark Phillips. IBM WebSphere MQ/ESB Technical Strategy - Clients & APIs.
(bluepages entry).
From: Mark Phillips/UK/IBM@IBMGB
To: public-soap-jms@w3.org
Date: 21/07/2009 16:27
Subject: Action 92: "Propose the wording for the change to split 2024 into three testable assertions"
Sent by: public-soap-jms-request@w3.org
In response to Action 92 [1] - "Propose the wording for the change to
split 2024 into three testable assertions":
I noticed that assertion Protocol-2024 [2] from the table in 2.2.4 actually
has a significant overlap with Protocol-2021 [3] in the requestURI property
description (section 2.2.3) which reads:
"Specifies the JMS URI of the service. The client MUST create this property
which is derived from the supplied URI. The client MUST remove the
targetService query parameter if specified; SHOULD remove JMS Message
Header properties; and MAY remove other query parameters (for example
client security related properties)."
I propose that we delete the Protocol-2024 assertion and enhance the
description of requestURI property in 2.2.3, reducing the scope of
Protocol-2021 to stating that the requestURI property must be included, and
adding two new mandatory testable assertions, and two optional statements.
We would do this by replacing the paragraph which begins "Specifies the JMS
URI of the service." with the following:
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Specifies the JMS URI of the service. The client MUST create this property
by deriving information from the supplied URI in the following way:
* The client MUST leave the destinationName as-is in the URI
* The client MUST remove the targetService and replyToName parameters if
specified;
* The client SHOULD remove deliveryMode, jndiConnectionFactoryName,
jndiInitialContextFactory, jndiURL, jndiContextParameter, timeToLive,
priority properties if specified
* The client MAY remove other query parameters not explicitly mentioned
above (for example client security related properties).
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
The first two bullets are the new testable assertions. This leaves us with
the following assertions:
(Protocol-2024 is deleted)
Protocol-2021: "The client MUST create this property by deriving
information from the supplied URI":
Protocol-????: "The client MUST leave the destinationName as-is in the
URI"
Protocol-????: "The client MUST remove the targetService and replyToName
parameters if specified"
[1] http://www.w3.org/2002/ws/soapjms/tracker/actions/92
[2] http://www.w3.org/TR/2009/CR-soapjms-20090604/#Protocol-2024
[3] http://www.w3.org/TR/2009/CR-soapjms-20090604/#Protocol-2021
Regards
Mark
Mark Phillips. IBM WebSphere MQ/ESB Technical Strategy - Clients & APIs.
(bluepages entry).
Received on Tuesday, 28 July 2009 15:57:39 UTC