sca-bindings message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Updated proposed resolution to issue BINDINGS-31
- From: Simon Holdsworth <simon_holdsworth@uk.ibm.com>
- To: sca-bindings@lists.oasis-open.org
- Date: Tue, 2 Dec 2008 13:53:38 +0000
Updated proposed resolution to issue
BINDINGS-31: What is a "plain name" for a connection factories
or activation specs, and how is one distinguished from a JNDI name?
Applies to the JMS binding specification cd01-rev3:
(updated to use "raise an error" and fix RFC2119
language)
rename "name" attribute to "jndiName".
Describe the jndiName attribute (in this example for a Destination) as
follows:
- binding.jms/destination/@jndiName
– the JNDI name of the JMS Destination that the binding uses to send or
receive messages. The behaviour of this attribute is determined by
the value of the @create attribute as follows:
- If the @create attribute value is "always"
then the @jndiName attribute is optional; if the destination cannot be
created at the specified location then the SCA runtime MUST raise an error.
If the @jndiName attribute is omitted this specification places no
restriction on the JNDI location of the created resource.
- If the @create attribute value is "ifnotexist"
then the @jndiName attribute MUST specify the location of the possibly
existing destination; if the destination does not exist at this location,
but cannot be created there then the SCA runtime MUST raise an error. If
the jndiName refers to an existing resource other than a JMS Destination
of the specified type then the SCA runtime MUST raise an error.
- If the @create attribute value is "never"
then the @jndiName attribute MUST specify the location of the existing
destination; If the destination is not present at the location, or the
location refers to a resource other than a JMS Destination of the specified
type then the SCA runtime MUST raise an error.
The "plain name" referred to in the current spec is really there
to be an attribute of the created resource. I think it makes more
sense then for that to be amongst the properties that are children of the
element, and not a standard attribute.
Remove the sentences that say "This
can either be a JNDI name or a plain connection factory name.".
as they are currently describing elements, not the name attribute
of those elements and so are just incorrect.
Update the examples to rename the "name" attribute to "jndiName",
and/or move to inside the resource element for creation examples as appropriate.
Update the XML schema to rename "name" to "jndiName",
and make the value type "anyURI".
Simon Holdsworth
STSM, SCA Bindings Architect; Master Inventor; OASIS SCA Bindings TC Chair
MP 211, IBM UK Labs, Hursley Park, Winchester SO21 2JN, UK
Tel +44-1962-815059 (Internal 245059) Fax +44-1962-816898
Internet - Simon_Holdsworth@uk.ibm.com
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]