|
|
This section is a landing page to organize work for BUG 7489289
See http://home.beasys.com/internal/docs/wiki/p/view/jms/queueNameSyntax
The Create Destination Identifier (CDI) is a reference name for a destination or a member of a distributed destination that provides a way to lookup a destination JNDI using the standard JMS javax.jms.Session
createQueue or
createTopic API.
This name must be unique within the scope of the JMS server to which this destination is targeted. However, it does not need to be unique within the scope of the entire JMS module. For example, two queues can have the same CDI name as long as those queues are targeted to different JMS servers.
| Note: | Since this name must be unique within the scope of a JMS server, verify whether other JMS modules may contain destination names that conflict with this name. It is the responsibility of the deployer to resolve the destination names targeted to JMS servers. |
+ (.|jms-server-name)/module-name!dest-name
+ (.|jms-server-name)/cdi-name
| Note: | When replacing "jms-server-name" with ".", the search is restricted to the JMS connection host rather than the entire cluster. |
| Note: | The local JNDI name only works when the "JNDI context host" is on the same server as the dest, the JNDI context host is __not__ necessarily the same as the "connection host". |
| Note: | In the CDI case when "jms-server-name" is replaced with ".", the API returns the first locally available/started member of the UDQ, in this scenario. |
+ (.|jms-server-name)/module-name!jms-server-name@udd-name
+ (.|jms-server-name)/cdi-name
NOTE: When replacing "jms-server-name" with ".", the search is restricted to the JMS connection host rather than the entire cluster.
In the CDI case when "jms-server-name" is replaced with ".", the API returns the first locally available/started member of the UDQ.
WDDs (weighted distributed destination) do not have the CDI parameter as the they dont extend destination-type in the schema. Specify a CDI on each member destination instead.
There is no way to get the logical UDD or WDD:
Doc is incorrect with respect to:
Following console help text that must point to the primary location of this usage syntax page:
Following pages should now be updated to reflect the fixes for bugs 7447348 & 7447386:
|