SOAP-JMS ACTION-79

Group,

Last meeting we agreed to modify the JMS URI specification so that the
Additional JNDI Parameters prefix (i.e. "jndi-") would be more
consistent with the SOAP over JMS specification.  The suggestion was to
replace the term "jndi-" with "jndiContextParameter-" in sections
4.2.1.4 and 4.2.2.1.

Since the goal is to make this functionality more consistent with the
SOAP over JMS specification, I also suggest changing the examples in
these sections.  I have listed the current sections along with the
potentially new sections below:


[CURRENT SECTION] 4.2.1.4.  Additional JNDI Parameters

   It is possible that connecting to a JNDI provider requires additional
   parameters.  These parameters can be passed in as custom parameters
   (see Section 4.4).  To identify a custom parameter as JNDI specific,
   the parameter name must start with the prefix "jndi-".

   For example, if the JNDI provider requires a parameter named
   com.sun.jndi.someParameter, you can supply the parameter in the URI
   as: jndi-com.sun.jndi.someParameter=someValue


[NEW SECTION] 4.2.1.4.  Additional JNDI Parameters

   It is possible that connecting to a JNDI provider requires additional
   parameters.  These parameters can be passed in as custom parameters
   (see Section 4.4).  To identify a custom parameter as JNDI specific,
   the parameter name must start with the prefix
"jndiContextParameter-".

   For example:

   To include the JNDI property com.acme.jndi.enable.tracing for the
ACME 
   Corporation JNDI provider, you would supply the parameter in the URI
as: 
   jndiContextParameter-com.acme.jndi.enable.tracing=someValue.

   To include the standard JNDI property java.naming.referral to disable
(ignore) JNDI provider 
   referrals, you would supply the parameter in the URI as: 
   jndiContextParameter-java.naming.referral=ignore.



[CURRENT SECTION] 4.2.2.1.  Performing a JNDI Look-up with Custom
Parameters

   Any custom parameters with a prefix of "jndi-" in the URI should be
   used when establishing a connection to the JNDI provider.  Before
   passing the custom parameter to the JNDI provider, remove the "jndi-"
   prefix as the prefix is for identifying the custom parameter in the
   URI only.

   For example, the JMS URI...

   jms:jndi:REQ_QUEUE?jndiURL=file:/C:/JMSAdmin
   &jndiInitialContextFactory=com.sun.jndi.fscontext.RefFSContextFactory
   &jndiConnectionFactoryName=CONNFACT
   &jndiContextParameter-com.sun.jndi.someParameter=someValue

   ...instructs the consumer to use the following properties to connect
   to the JNDI provider:

   java.naming.provider.url=file:/C:/JMSAdmin
 
java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory
   com.sun.jndi.someParameter=someValue



[NEW SECTION] 4.2.2.1.  Performing a JNDI Look-up with Custom Parameters

   Any custom parameters with a prefix of "jndiContextParameter-" in the
URI should be
   used when establishing a connection to the JNDI provider.  Before
   passing the custom parameter to the JNDI provider, remove the
"jndiContextParameter-"
   prefix as the prefix is for identifying the custom parameter in the
   URI only.

   For example, the JMS URI...

   jms:jndi:REQ_QUEUE?jndiURL=file:/C:/JMSAdmin
   &jndiInitialContextFactory=com.sun.jndi.fscontext.RefFSContextFactory
   &jndiConnectionFactoryName=CONNFACT
   &jndiContextParameter-com.acme.jndi.enable.tracing=someValue

   ...instructs the consumer to use the following properties to connect
   to the JNDI provider:

   java.naming.provider.url=file:/C:/JMSAdmin
 
java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory
   com.acme.jndi.enable.tracing=someValue



Regards,
Derek