6 Replies Latest reply on Jun 10, 2008 10:34 AM by Brian Stansberry

    Inconsistent usage of the Ejb3Deployment.deploymentScope fie

    Brian Stansberry Master

      Seeing some inconsistent usage of the org.jboss.ejb3.Ejb3Deployment class' deploymentScope field. This may be just due to ongoing refactoring, but want to point it out.

      Looks like Ejb3Deployment treats the deploymentScope field as indicating the presence of an ear in the deployment -- see the getEar() and getApplication() methods which return it. But looking at Ejb3Deployer.deploy() in the AS, it looks like a JBoss5DeploymentScope will be created and passed to the Ejb3Deployment whether or not the deployment is an ear.

      One place this shows up is in the creation of ObjectNames for beans. For example, deploying a bean named VMTrackerBean in a clusteredsession-test.jar with no enclosing ear results in the following object name for the bean:

      jboss.j2ee:ear=clusteredsession-test.jar,jar=clusteredsession-test.jar,name=VMTrackerBean,service=EJB3