The following conventions apply to all Java EE deployment descriptor elements unless indicated otherwise. - In elements that specify a pathname to a file within the same JAR file, relative filenames (i.e., those not starting with "/") are considered relative to the root of the JAR file's namespace. Absolute filenames (i.e., those starting with "/") also specify names in the root of the JAR file's namespace. In general, relative names are preferred. The exception is .war files where absolute names are preferred for consistency with the Servlet API. The jmx-name element allows one to specify the JMX ObjectName to use for the MBean associated with the ejb-jar module. This must be a unique name and valid JMX ObjectName string. The security-domain element specifies the JNDI name of the security manager that implements the EJBSecurityManager and RealmMapping for the domain. When specified at the jboss level it specifies the security domain for all j2ee components in the deployment unit. One can override the global security-domain at the container level using the security-domain element at the container-configuration level. The security-role element contains the definition of a security role. The definition consists of an the security role name and principal name element(s). The principal-name element is the name of the principal that is mapped to the assembly role-name. The depends element gives a JMX ObjectName of a service on which the container or ejb depends. (default) The JNDI name under with the local interface should be bound. If it is not provided jboss will assume "jndi-name" = "beanClass/local" The ejb-ref element is used to give the jndi-name of an external ejb reference. In the case of an external ejb reference, you don't provide a ejb-link element in ejb-jar.xml, but you provide a jndi-name in jboss.xml Used in: entity, session, message-driven, consumer, and service The ejb-local-ref element is used to give the jndi-name of an external ejb reference. In the case of an external ejb reference, you don't provide a ejb-link element in ejb-jar.xml, but you provide a jndi-name in jboss.xml The resource-ref element gives a mapping between the "code name" of a resource (res-ref-name, provided by the Bean Developer) and its "xml name" (resource-name, provided by the Application Assembler). If no resource-ref is provided, jboss will assume that "xml-name" = "code name" See resource-managers. The res-ref-name element specifies the name of a resource manager connection factory reference. The name is a JNDI name relative to the java:comp/env context. The name must be unique within a Deployment File. The res-type element specifies the type of the data source. The type is specified by the fully qualified Java language class or interface expected to be implemented by the data source. The service-ref-name element gives the ENC relative name used in the ejb-jar.xml service-ref-name element. jboss.test:loader=cts-cmp2v1-sar.ear dot.com:loader=unique-archive-name java2ParentDelegaton=true ]]> The loader-repository-config element specifies any arbitrary configuration fragment for use in configuring the loader-repository instance. The actual content of this element is specific to the loaderRepositoryClass and the code parsing the element. OrganizationService file:/wsdlRepository/organization-service.wsdl OrganizationService Secure Client Config META-INF/jbossws-client-config.xml META-INF/jbossws-client-handlers.xml SecureService org.jboss.tests.ws.jaxws.webserviceref.SecureEndpointService {http://org.jboss.ws/wsref}SecureEndpointService org.jboss.tests.ws.jaxws.webserviceref.SecureEndpoint {http://org.jboss.ws/wsref}SecureEndpointPort javax.xml.ws.security.auth.username kermit javax.xml.ws.security.auth.password thefrog ]]> The message-destination element is used to configure the jndi-name for a message-destination in ejb-jar.xml Used in: assembly-descriptor