Package org.jboss.as.ee.component.deployers

Class EarApplicationNameProcessor

java.lang.Object

org.jboss.as.ee.component.deployers.EarApplicationNameProcessor

All Implemented Interfaces:

org.jboss.as.server.deployment.DeploymentUnitProcessor

public class EarApplicationNameProcessor
extends Object
implements org.jboss.as.server.deployment.DeploymentUnitProcessor

The Java EE6 spec and Enterprise Beans 3.1 spec contradict each other on what the "application-name" semantics are. The Java EE6 spec says that in the absence of a (top level) .ear, the application-name is same as the (top level) module name. So if a blah.jar is deployed, as per Java EE6 spec, both the module name and application name are "blah". This is contradictory to the Enterprise Beans 3.1 spec (JNDI naming section) which says that in the absence of a (top level) .ear, the application-name is null.

This deployment processor, sets up the Attachments.EAR_APPLICATION_NAME attachment with the value that's semantically equivalent to what the Enterprise Beans 3.1 spec expects.

Author:

Jaikiran Pai

Constructor Summary

Constructors

Constructor	Description
EarApplicationNameProcessor()

Method Summary

Modifier and Type	Method	Description
void	deploy(org.jboss.as.server.deployment.DeploymentPhaseContext phaseContext)

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Methods inherited from interface org.jboss.as.server.deployment.DeploymentUnitProcessor

undeploy

Constructor Detail

EarApplicationNameProcessor

public EarApplicationNameProcessor()

Method Detail

deploy

public void deploy(org.jboss.as.server.deployment.DeploymentPhaseContext phaseContext)
            throws org.jboss.as.server.deployment.DeploymentUnitProcessingException

Specified by:

deploy in interface org.jboss.as.server.deployment.DeploymentUnitProcessor

Throws:

org.jboss.as.server.deployment.DeploymentUnitProcessingException