The name of the global directory. The path of the global directory. The name of another previously named path, or of one of the standard paths provided by the system. If 'relative-to' is provided, the value of the 'path' attribute is treated as relative to the path specified by this attribute. Flag indicating whether each of the subdeployments within a .ear can access classes belonging to another subdeployment within the same .ear. Setting this to false, allows the subdeployments to see classes belonging to other subdeployments within the .ear. For example: myapp.ear | |--- web.war | |--- ejb1.jar | |--- ejb2.jar If the ear-subdeployments-isolated is set to false, then the classes in web.war can access classes belonging to ejb1.jar and ejb2.jar. Similarly, classes from ejb1.jar can access classes from ejb2.jar (and vice-versa). *Note that this flag, has no effect on the isolated classloader of the .war file(s). i.e. irrespective of whether this flag is set to true or false, the .war within a .ear will have a isolated classloader and other subdeployments within that .ear will not be able to access classes from that .war. This is as per spec* Flag indicating whether system property replacement will be performed on a descriptor. This defaults to true, however it is disabled in the default configurations. Security Node: System properties etc are resolved in the security context of the application server itself, not the deployment that contains the file. This means that if you are running with a security manager and enable this property, a deployment can potentially access system properties or environment entries that the security manager would have otherwise prevented. Flag indicating whether system property replacement will be performed on an annotation. This defaults to true, however it is disabled in the default configurations. Security Node: System properties etc are resolved in the security context of the application server itself, not the deployment that contains the file. This means that if you are running with a security manager and enable this property, a deployment can potentially access system properties or environment entries that the security manager would have otherwise prevented. Configures EE Concurrent resources. If undefined, it turns off all EE Concurrent functionality. The context service (implementing javax.enterprise.concurrent.ContextService). The optional attribute that defines if the context service should use a transaction setup provider, which may be used to suspend and resume active transactions. A managed thread factory (implementing javax.enterprise.concurrent.ManagedThreadFactory). The mandatory "name" attribute, which may not be empty or have the value "default", identifies the created thread factory. The optional "context-service" identifies which Context Service should be used by created threads. The optional "priority" attribute may be used to specify the priority of created threads. A managed executor service (implementing javax.enterprise.concurrent.ManagedExecutorService). Deprecated. Managed executors always use their own thread factory, and to configure its threads priority use instead thread-priority attribute. The minimum number of threads to be used by the executor. If left undefined the default core-size is calculated based on the number of processors. A value of zero is not advised and in some cases invalid. See the queue-length attribute for details on how this value is used to determine the queuing strategy. The maximum number of threads to be used by the executor. If left undefined the value from core-size will be used. This value is ignored if an unbounded queue is used (only core-threads will be used in that case). The executors task queue capacity. A length of 0 means direct hand-off and possible rejection will occur. An undefined length (the default), or Integer.MAX_VALUE, indicates that an unbounded queue should be used. All other values specify an exact queue size. If an unbounded queue or direct hand-off is used, a core-threads value greater than zero is required. A managed scheduled executor service (implementing javax.enterprise.concurrent.ManagedScheduledExecutorService). Deprecated. Managed executors always use their own thread factory, and to configure its threads priority use instead thread-priority attribute. A non empty token name. The name for an EE Concurrency resource. The name of the entry in JNDI. The name of the context service to be used. Deprecated. Use thread-priority instead to configure executor's thread priority. A priority which can range from 1 to 10 (inclusive). See http://java.sun.com/javase/6/docs/api/java/lang/Thread.html#setPriority(int) for more information. This type matches EE Concurrent 1.0 Final Release attribute named "Priority", defined in sections 3.4.4.2 The amount of time in milliseconds that a task can execute before it is considered hung. If zero then tasks are never considered hung. This xml attribute matches EE Concurrent 1.0 Final Release attribute named "Hung Task Threshold", defined in sections 3.1.4.2 and 3.2.4.2 If the application intends to run short vs. long-running tasks they can specify to use pooled or daemon threads. This xml attribute matches EE Concurrent 1.0 Final Release attribute named "Thread Use", defined in section 3.2.4.2 The number of threads to keep in the executor's pool, even if they are idle. This type matches EE Concurrent 1.0 Final Release attribute named "Pool Info: Core Size", defined in sections 3.1.4.2 and 3.2.4.2 The maximum number of threads to allow in the executor's pool. This type matches EE Concurrent 1.0 Final Release attribute named "Pool Info: Maximum Size", defined in section 3.1.4.2 The time to allow threads to remain idle when the number of threads is greater than the core size. This type matches EE Concurrent 1.0 Final Release attribute named "Pool Info: Keep Alive", defined in sections 3.1.4.2 and 3.2.4.2 The number of tasks that can be stored in the input queue. Zero means the queue capacity is not limited. This type matches EE Concurrent 1.0 Final Release attribute named "Work Queue Capacity", defined in section 3.1.4.2 The policy to use when a task is to be rejected by the executor. This type matches EE Concurrent 1.0 Final Release attribute named "Reject Policy", defined in sections 3.1.4.2 and 3.2.4.2 Throw an exception when rejected. Automatically resubmit and abort if it fails. The JNDI names for the default resources on EE components/modules JNDI contexts. The optional context-service attribute defines the JNDI name of the EE Concurrency ContextService that should be bound at java:comp/DefaultContextService. The optional datasource attribute defines the JNDI name of the SQL DataSource that should be bound at java:comp/DefaultDataSource. The optional jms-connection-factory attribute defines the JNDI name of the JMS ConnectionFactory that should be bound at java:comp/DefaultJMSConnectionFactory. The optional managed-executor-service attribute defines the JNDI name of the EE Concurrency ManagedExecutorService that should be bound at java:comp/DefaultManagedExecutorService. The optional managed-scheduled-executor-service attribute defines the JNDI name of the EE Concurrency ManagedScheduledExecutorService that should be bound at java:comp/DefaultManagedScheduledExecutorService. The optional managed-thread-factory attribute defines the JNDI name of the EE Concurrency ManagedThreadFactory that should be bound at java:comp/DefaultManagedThreadFactory.