A product specific name that this message destination should be mapped to. Each message-destination-ref element that references this message destination will define a name in the namespace of the referencing component. (It's a name in the JNDI java:comp/env namespace.) Many application servers provide a way to map these local names to names of resources known to the application server. This mapped name is often a global JNDI name, but may be a name of any form. Each of the local names should be mapped to this same global name. Application servers are not required to support any particular form or type of mapped name, nor the ability to use mapped names. The mapped name is product-dependent and often installation-dependent. No use of a mapped name is portable. |
QName | Type | Fixed | Default | Use | Inheritable | Annotation |
---|---|---|---|---|---|---|
id | xsd:ID | optional |
<xsd:element name="mapped-name" type="javaee:xsdStringType" minOccurs="0"> <xsd:annotation> <xsd:documentation> <![CDATA[ A product specific name that this message destination should be mapped to. Each message-destination-ref element that references this message destination will define a name in the namespace of the referencing component. (It's a name in the JNDI java:comp/env namespace.) Many application servers provide a way to map these local names to names of resources known to the application server. This mapped name is often a global JNDI name, but may be a name of any form. Each of the local names should be mapped to this same global name. Application servers are not required to support any particular form or type of mapped name, nor the ability to use mapped names. The mapped name is product-dependent and often installation-dependent. No use of a mapped name is portable. ]]> </xsd:documentation> </xsd:annotation> </xsd:element> |