ISSUE-24: Precedence rules for jndiContextParameter


Precedence rules for jndiContextParameter

SOAP-JMS Binding specification
Raised by:
Mark Phillips
Opened on:
In section 2.2.1 the spec. states that the jndiContextParameter may be specified more than once. This could cause confusion with the earlier assertions Protocol-2001 in 2.2 that states "If a given property is specified in more than one of these, the following list specifies the precedence: the first MUST be used in preference to the second." and Protocol-2002: "If a given property is specified more than once in the JMS URI the last instance of the property MUST be used."


In section 2.2.1, in the description of the jndiContextParameter parameter, change the second bullet from:

An optional property that MAY be specified more than once.


An optional property that MAY be specified more than once. When determining precedence rules for multiple occurrences of the jndiContextParameter property, the property is not considered to be occur more than once unless the name attribute is identical in multiple jndiContextParameter properties.
Related Actions Items:
No related actions
Related emails:
  1. Applied resolution for issue 24 (ACTION-140) (from on 2010-02-16)
  2. Agenda for 2010-02-09 conference call (from on 2010-02-08)
  3. Agenda for 2010-02-02 conference call (from on 2010-02-01)
  4. Agenda for the 2010-01-26 conference call (from on 2010-01-25)
  5. ISSUE-24 (mphillip): Precedence rules for jndiContextParameter [SOAP-JMS Binding specification] (from on 2010-01-25)

Related notes:

Opened as per conference call of 2010-01-26:

Eric Johnson, 2 Feb 2010, 00:03:00

Applied resolution accepted as per:

Eric Johnson, 23 Feb 2010, 00:50:25

Display change log ATOM feed

Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: 24.html,v 1.1 2013-09-16 14:06:35 carine Exp $