[
https://issues.jboss.org/browse/AS7-2634?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas resolved AS7-2634.
---------------------------------
Resolution: Done
This will now throw an exception.
We do not automatically determine the bean type from an existing annotation for two
reasons:
- We are not required to via the spec. If we allowed this it would be as a spec
extension.
- This would require adding an additional phase to make sure the composite annotation
index information for all deployments is available in the PARSE phase, which is to big a
change to make this late in the release cycle.
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.Final
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