ISSUE-25: URI example for jndiContextParameter

mphillip

URI example for jndiContextParameter

State:

CLOSED

Product:

SOAP-JMS Binding specification

Raised by:

Mark Phillips

Opened on:

2010-01-25

Description:

Section 2.2.1 includes WSDL examples for the jndiContextParameter but no URI example.

Proposal:

Change the first jndiContextParameter example so that it includes both WSDL and URI snippets. i.e. replace:

Example: Including the JNDI property com.acme.jndi.enable.tracing for the ACME Corporation JNDI provider
<soapjms:jndiContextParameter name="com.acme.jndi.enable.tracing" value=true" />

...with:

Example: Including the JNDI property com.acme.jndi.enable.tracing for the ACME Corporation JNDI provider
WSDL:
<soapjms:jndiContextParameter name="com.acme.jndi.enable.tracing" value=true" />
URI:
jndi-com.acme.jndi.enable.tracing=true

...and change the second jndiContextParameter example in the same way, so that:

Example: Including the standard JNDI property java.naming.referral to disable (ignore) JNDI provider referrals.
<soapjms:jndiContextParameter name="java.naming.referral" value="ignore" />

...becomes:

Example: Including the standard JNDI property java.naming.referral to disable (ignore) JNDI provider referrals.
WSDL:
<soapjms:jndiContextParameter name="java.naming.referral" value="ignore" />
URI:
jndi-java.naming.referral=ignore

Related Actions Items:

No related actions

Related emails:

1. Applied resolution for issue 25 (ACTION-139) (from M8PHILLI@uk.ibm.com on 2010-02-16)
2. Agenda for 2010-02-09 conference call (from eric@tibco.com on 2010-02-08)
3. Agenda for 2010-02-02 conference call (from eric@tibco.com on 2010-02-01)
4. Action136 - revised proposal for Issue 25 (from M8PHILLI@uk.ibm.com on 2010-01-29)
5. Agenda for the 2010-01-26 conference call (from eric@tibco.com on 2010-01-25)
6. ISSUE-25 (mphillip): URI example for jndiContextParameter [SOAP-JMS Binding specification] (from sysbot+tracker@w3.org on 2010-01-25)

Related notes:

Display change log