Re: [sca-bindings] BINDINGS-103: optional used in normative statement

Logged as: http://www.osoa.org/jira/browse/BINDINGS-103

-Eric.

Simon Holdsworth wrote:

  TARGET: SCA JMS Binding
Specification
CD-03
  

  

  DESCRIPTION: 
  

  

  BJM30011 uses the RFC2119 keyword
"optional".
 the statement needs rewording
  

  
If the @create attribute value for a
destination,
connectionFactory or activationSpec element is "always" then
the @jndiName attribute is optional; if the resource cannot be created
at the specified location then the SCA runtime MUST raise an error
  

  

  PROPOSAL:
  

  

  reword the statement 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
  

  

  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