- From: Mark Phillips <M8PHILLI@uk.ibm.com>
- Date: Tue, 16 Feb 2010 10:48:11 +0000
- To: public-soap-jms@w3.org
I've applied the changes for ACTION-139 [1] / ISSUE-25 [2] as agreed in the call dated 2010/02/09 [3]. This completes action 139. HTML of the previous binding spec is available here: http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?rev=1.74&content-type=text/html&f=h#binding-connection and the updated binding spec is here: http://dev.w3.org/cvsweb/~checkout~/2008/ws/soapjms/soapjms.html?rev=1.75&content-type=text/html&f=h #binding-connection Specifically: ============= Replace the existing samples with sample 1... = = = = = = = = = = = = = = = = = = = = == = = Example: Including JNDI context properties in WSDL = = = = = = = = = = = = = = = = = = = = == = = <!-- Enable tracing for the ACME Corporation JNDI provider -->? <soapjms:jndiContextParameter name="com.acme.jndi.enable.tracing" value="true" /> <!-- Include the standard JNDI property to ignore JNDI provider referrals --> <soapjms:jndiContextParameter name="java.naming.referral" value="ignore" /> = = = = = = = = = = = = = = = = = = = = == = = ...and sample 2: = = = = = = = = = = = = = = = = = = = = == = = Example: Including JNDI context properties in URI = = = = = = = = = = = = = = = = = = = = == = = jms:jndi:destinationName?jndi-com.acme.jndi.enable.tracing=true&jndi-java.naming.referral=ignore = = = = = = = = = = = = = = = = = = = = == = = ================================================================= This is a link to view the differences: http://dev.w3.org/cvsweb/2008/ws/soapjms/soapjms.html.diff?r1=1.74&r2=1.75&f=h ...and this is a link to view the differences from the previous XML Spec version: http://dev.w3.org/cvsweb/2008/ws/soapjms/soapjms.xml.diff?r1=1.75&r2=1.76&f=h [1] http://www.w3.org/2002/ws/soapjms/tracker/actions/139 [2] http://www.w3.org/2002/ws/soapjms/tracker/issues/25 [3] http://www.w3.org/2010/02/09-soap-jms-minutes.html Regards Mark
Received on Tuesday, 16 February 2010 10:54:28 UTC