Oracle® Containers for J2EE Enterprise JavaBeans Developer's Guide 10g (10.1.3.5.0) Part Number E13981-01 |
|
|
View PDF |
Using JMS 1.1, you define an environment reference to a JMS connection resource manager connection factory the same as you do in JMS 1.0 (see "Configuring an Environment Reference to a JMS Destination or Connection Resource Manager Connection Factory (JMS 1.0)"). However, you can define an environment reference to a JMS destination using a <message-destination-ref>
element in the client deployment descriptor and a <message-destination-ref-mapping>
element in the corresponding OC4J-specific deployment descriptor (see "Where do you Configure an EJB Environment Reference?").
You use the <message-destination-ref-mapping>
to map the client <message-destination-ref-name>
to another location that is available in the OC4J environment. This provides the means of linking message consumers and producers to one or more common logical destinations.
You can use <message-destination-ref>
in all EJB types, therefore <message-destination-ref-mapping>
is not restricted to message-driven deployment.
For more information, see "Oracle Enterprise Messaging Service (OEMS)" in the Oracle Containers for J2EE Services Guide.
Note:
In EJB 3.0, an environment reference to a resource manager connection factory is not needed. You can access a resource manager connection factory directly using resource injection (see "Looking Up an EJB 3.0 Resource Manager Connection Factory").For information on looking up a resource manager connection factory, see the following: