J2EE 5.0 complexType message-destinationType

Abstract	false (This can be used in an instance)
Target Namespace	http://java.sun.com/xml/ns/javaee
Declared Namespaces	xmlns:javaee=http://java.sun.com/xml/ns/javaee xmlns:xsd=http://www.w3.org/2001/XMLSchema

<xsd:complexType name="message-destinationType">
    <xsd:annotation>
        <xsd:documentation>
The message-destinationType specifies a message
destination. The logical destination described by this
element is mapped to a physical destination by the Deployer.

The message destination element contains:

- an optional description
- an optional display-name
- an optional icon
- a message destination name which must be unique
among message destination names within the same
Deployment File.
- an optional mapped name

Example:

<message-destination>
<message-destination-name>CorporateStocks
</message-destination-name>
</message-destination>
        </xsd:documentation>
    </xsd:annotation>
    <xsd:sequence>
        <xsd:group ref="javaee:descriptionGroup"/>
        <xsd:element name="message-destination-name" type="javaee:string">
            <xsd:annotation>
                <xsd:documentation>
The message-destination-name element specifies a
name for a message destination. This name must be
unique among the names of message destinations
within the Deployment File.
                </xsd:documentation>
            </xsd:annotation>
        </xsd:element>
        <xsd:element name="mapped-name" type="javaee:xsdStringType" minOccurs="0">
            <xsd:annotation>
                <xsd:documentation>
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>
    </xsd:sequence>
    <xsd:attribute name="id" type="xsd:ID"/>
</xsd:complexType>

complexType {http://java.sun.com/xml/ns/javaee}message-destinationType

Source

Documentation