Index Changes
Page Difference

Difference between version and version     

Back to JMSBC_WSDL Xtensibility, or JMSBC_WSDL Xtensibility Info


At line 55 changed 1 line.
This example shows that the jndiConnectionFactoryName is "MyXATopicCF". Assuming that the JMS binding operation's {{destinationType}} value is "Queue" and that the {{Transaction}} value is "XATransaction", then the connection factory type being looked up is of type {{javax.jms.XAQueueConnectionFactory}}. It is the responsibility of the user to ensure that the connection factory bound to JNDI as "MyXAQueueCF" is of type {{javax.jms.XAQueueConnectionFactory}}. When JNDI is used, additional information needed to create the {{javax.naming.InitialContext}} must be specified by using the {{jndienv}} extensibility element. See additional details below on how to use the {{jndienv}} extensibility element to configure the JNDI environment information.
This example shows that the connectionFactoryName is "MyXATopicCF". Assuming that the JMS binding operation's {{destinationType}} value is "Queue" and that the {{Transaction}} value is "XATransaction", then the connection factory type being looked up is of type {{javax.jms.XAQueueConnectionFactory}}. It is the responsibility of the user to ensure that the connection factory bound to JNDI as "MyXAQueueCF" is of type {{javax.jms.XAQueueConnectionFactory}}. When JNDI is used, additional information needed to create the {{javax.naming.InitialContext}} must be specified by using the {{jndienv}} extensibility element. See additional details below on how to use the {{jndienv}} extensibility element to configure the JNDI environment information.
G'day, Anonymous Guest

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-16) was last changed on 01-May-07 12:16 PM, -0700 by jamestran