- From: Rokicki, Derek <Derek.Rokicki@softwareag.com>
- Date: Mon, 20 Oct 2008 17:16:26 -0400
- To: <public-soap-jms@w3.org>
With respect to action 45: http://www.w3.org/2002/ws/soapjms/tracker/actions/45 I propose we add the following sections to the URI scheme draft: http://www.ietf.org/internet-drafts/draft-merrick-jms-uri-04.txt 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 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, this JMS URI... jms:jndi:REQ_QUEUE?jndiURL=file:/C:/JMSAdmin &jndiInitialContextFactory=com.sun.jndi.fscontext.RefFSContextFactory &jndiConnectionFactoryName=CONNFACT &jndi-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
Received on Monday, 20 October 2008 21:17:09 UTC