[jboss-jira] [JBoss JIRA] Commented: (JBMETA-11) Defining a home-jndi-name for an EJB 3 bean is illegal

[Alexey Loubyansky (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBMETA-11?page=comments#action_12406633 ] 
            
Alexey Loubyansky commented on JBMETA-11:
-----------------------------------------

I added a method called checkValid() to JBossEnterpriseBeanMetaData. The only class that actually has something meaningful in it is the JBossSessionBeanMetaData. This is where this issue is fixed.
Currently, this method is called from JBossEnterpriseBeansMetaData.merge(...). Since this method seems to be always called (JBossEnterpriseBeanMetaData.merge(..) is not always called, depends on what kind of metadata is available).

Here is the current logic from checkValid for the session bean:
         // this is how the ejb3 deployer determines whether it's ejb3 module or not
         if(!(getEjbJarMetaData().isEJB1x() || getEjbJarMetaData().isEJB2x()))
         {
            if(this.home == null && this.homeJndiName != null)
               throw new IllegalStateException(
                  "EJB3 bean " + getEjbName() +
                  " doesn't define home interface but defines home-jndi-name '" +
                  this.homeJndiName + "' in jboss.xml");
            if(this.localHome == null && this.localHomeJndiName != null)
               throw new IllegalStateException(
                  "EJB3 bean " + getEjbName() +
                  " doesn't define local-home interface but defines local-home-jndi-name '" +
                  this.localHomeJndiName + "' in jboss.xml");
         }

> Defining a home-jndi-name for an EJB 3 bean is illegal
> ------------------------------------------------------
>
>                 Key: JBMETA-11
>                 URL: http://jira.jboss.com/jira/browse/JBMETA-11
>             Project: JBoss Metadata
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.0.0.Beta6
>            Reporter: Alexey Loubyansky
>         Assigned To: Alexey Loubyansky
>             Fix For: 1.0.0.CR1
>
>
> This issue is opened for EJBTHREE-1235.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira