[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1969) EJB3 deployments lead to java.lang.IllegalStateException: Null beannMetaData

[Brad Maxwell (JIRA)]

    [ https://jira.jboss.org/jira/browse/EJBTHREE-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12498197#action_12498197 ] 

Brad Maxwell commented on EJBTHREE-1969:
----------------------------------------

There seems to be a bug when you have the following situation.

ear/ 
ear/META-INF/application.xml (only has ejb2.jar listed as <module><ejb>ejb2.jar</ejb></module> )
ear/lib/ejb1.jar
ear/ejb2.jar

ejb2 has a private @EJB EJB2Interface bean;

The workaround is to move ejb1.jar out of lib to the root of the ear and list it in the application.xml

See attached examples.

> EJB3 deployments lead to java.lang.IllegalStateException: Null beannMetaData 
> -----------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1969
>                 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1969
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: 1.1.22
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>
> There has been more than one instance where users have reported issues around EJB3 deployments which leads to exception like this:
> Caused by: java.lang.IllegalStateException: Null beannMetaData
> at org.jboss.ejb3.interceptors.metadata.BeanInterceptorMetaDataBridge.setupMetaDataLists(BeanInterceptorMetaDataBridge.java:315)
> at org.jboss.ejb3.interceptors.metadata.BeanInterceptorMetaDataBridge.initialise(BeanInterceptorMetaDataBridge.java:235)
> at org.jboss.ejb3.interceptors.metadata.BeanInterceptorMetaDataBridge.(BeanInterceptorMetaDataBridge.java:138)
> at org.jboss.ejb3.interceptors.metadata.AdditiveBeanInterceptorMetaDataBridge.(AdditiveBeanInterceptorMetaDataBridge.java:48)
> at org.jboss.ejb3.aop.BeanContainer.initialize(BeanContainer.java:194)
> at org.jboss.ejb3.EJBContainer.(EJBContainer.java:249) 
> One such forum thread discussion is referenced in this JIRA. The issue appears to be around the way the deployment has been packaged. This needs more investigation and a fix (or an explanation about why this happens and the correct way to package the culprit application).  

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