W3C home > Mailing lists > Public > public-soap-jms@w3.org > October 2009

NEW ISSUE: Statement 3004 lacks context, RFC 2119 keywords

From: Eric Johnson <eric@tibco.com>
Date: Mon, 26 Oct 2009 15:15:06 -0700
Message-ID: <4AE61F6A.3080104@tibco.com>
To: SOAP-JMS <public-soap-jms@w3.org>
Description:

The supposedly normative statement 3004 currently reads:
"SOAP/JMS properties which are declarable in WSDL 1.1 and WSDL 2.0
documents†"

This doesn't stand on its own, and it doesn't have RFC 2119 keywords.
Further soapAction is not really a SOAP/JMS property.

The point of the statement seems to be (based on WG discussions
http://www.w3.org/2009/10/20-soap-jms-minutes.html) that this
specification only defines what these elements mean in these specific
WSDL locations, and no others.  What we want, then, is a normative
statement that says that a conforming implementation MUST use these
properties when found in those specific contexts, while saying nothing
about what they might mean in other contexts.

Proposal:

Replace the text of Section 3.6 with:

The XML elements jndiConnectionFactoryName, jndiInitialContextFactory,
jndiURL, deliveryMode, priority, timeToLive, and replyToName, in the
soapjms namespace, MUST be supported when used in the context of the
WSDL service, port/endpoint, and binding elements.  This specification
does not define any use outside of those elements.

Section 3.6.1:
Replace: "For this specification, each property in the table above adds
a WSDL Component Model Property with the same name to the containing
WSDL 2.0 component."

with:
"For this specification, each property in the list
jndiConnectionFactoryName, jndiInitialContextFactory, jndiURL,
deliveryMode, priority, timeToLive, and replyToName, adds a WSDL
Component Model Property with the same name to the containing WSDL 2.0
component.

-Eric.
Received on Monday, 26 October 2009 22:15:24 GMT

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