web server - Borland Technical Publications

Obtaining JMS Connection Factories and Destinations in J2EE Application Components
the element in the deployed DAR where the connection factory is
defined.
Just as the element is used to map logical names for JMS connection
factories to actual JNDI location of desired connection factory definition, the
element maps the logical name for JMS destinations, such as Queues and
Topics, to actual JNDI location of destination definition. The DTD representation of this
element for Borland deployment descriptors is as follows:
Two elements are specified:
■
resource-env-ref-name: this is the logical name of the Topic or Queue, and its
value must be identical to the value of the of J2EE standard
descriptor.
■
jndi-name: this is the JNDI name of the topic or queue that resolves the logical
name.
The final contents for Borland descriptor ejb-borland.xml accompanying the ejbjar.xml
defined above is:
session_bean
...
jms/MyJMSQueueConnectionFactory
resources/qcf
jms/MyJMSQueue
resources/q
...
Note that the elements from both descriptor files are identical.
Keep in mind that and elements can be used for all
J2EE components that require JMS related resource objects. For instance, application
clients using JMS APIs should obtain connection factories and destinations the same
way as EJBs, through JNDI lookup or Resource References in application code and
specification of and elements in the clients
deployment descriptors. For example, in the J2EE standard descriptor, applicationclient.xml:
...
jms/MyJMSTopicConnectionFactory
javax.jms.TopicConnectionFactory
Application
jms/MyJMSTopic
javax.jms.Topic
...
Chapter 23: Using JMS 215