Updated proposal for issue BINDINGS-103

This issue is around the use of "optional"
in a normative statement.  However in looking at other issues I noticed
that the attribute which is stated as being "optional" is actually
defined in the JMS binding spec as being required.  The description
is correct, so the pseudo schema and schema need to be updated.  So
here's the revised proposal:

Reword BJM30011 as follows:

If the @create attribute value for a
destination, connectionFactory or activationSpec element is "always"
and the @jndiName attribute is present and the resource cannot be created
at the location specified by the @jndiName attribute, then the SCA runtime
MUST raise an error [BJM30011]

Change the jndiName attribute for the
destination, connectionFactory and activationSpec elements in the pseudoschema
to include a "?" indicating optionality.

Change the jndiName attribute schema
for the destination, connectionFactory and activationSpec elements to remove
'required="true" '.

Regards, Simon

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 - 

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