[jboss-jira] [JBoss JIRA] (AS7-2634) SessionBeanComponentDescriptionFactory silently ignores EJBs declared in ejb-jar.xml
Richard Opalka (Commented) (JIRA)
jira-events at lists.jboss.org
Wed Nov 16 03:22:40 EST 2011
[ https://issues.jboss.org/browse/AS7-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643219#comment-12643219 ]
Richard Opalka commented on AS7-2634:
-------------------------------------
The pull request I sent to upstream
https://github.com/jbossas/jboss-as/pull/662
contains test
https://github.com/ropalka/jboss-as/commit/f398455b81e72799015c17d7b3f24876403adc71
To reproduce the issue just delete line
<session-type>Stateless</session-type>
from ejb-jar.xml for StatelessBean2. The test will start failing.
> SessionBeanComponentDescriptionFactory silently ignores EJBs declared in ejb-jar.xml
> ------------------------------------------------------------------------------------
>
> Key: AS7-2634
> URL: https://issues.jboss.org/browse/AS7-2634
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB
> Reporter: Richard Opalka
> Assignee: Stuart Douglas
> Priority: Critical
> Fix For: 7.1.0.CR1
>
>
> If I'm trying to provide another EJB in ejb-jar.xml that is using different name than
> the name derived from its class (I'm trying to provide multiple EJBs based on same class
> with different names), my bean is silently ignored by the following piece of code:
> {code:title=SessionBeanComponentDescriptionFactory.java|borderStyle=solid}
> ...
> final SessionType sessionType = sessionBean.getSessionType();
> if(sessionType == null && sessionBean instanceof GenericBeanMetaData) {
> //TODO: this is a hack
> return;
> }
> ...
> {code}
> The code should
> * either detect bean type according to its associated class annotation (@Singleton, @Stateless) for EJB3 beans
> * or print warning or throw exception that <session-type> must be provided in ejb-jar.xml descriptor for EJB21 endpoints
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list