]
jaikiran pai updated JBMETA-330:
--------------------------------
Fix Version/s: jboss-metadata-ejb-2.0.0-alpha-30
(was: jboss-metadata-ejb-2.0.0-alpha-29)
Affects Version/s: jboss-metadata-ejb-2.0.0-alpha-29
@Startup annotation and init-on-startup element in ejb-jar.xml
aren't merged into metadata correctly
----------------------------------------------------------------------------------------------------
Key: JBMETA-330
URL:
https://issues.jboss.org/browse/JBMETA-330
Project: JBoss Metadata
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: ejb
Affects Versions: jboss-metadata-ejb-2.0.0-alpha-28,
jboss-metadata-ejb-2.0.0-alpha-29
Environment: JBoss AS 6.0.0.Final
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: jboss-metadata-ejb-2.0.0-alpha-30
Consider the following bean:
{code}
@Singleton
@Startup
public class StartupBean
{
...
}
{code}
and the corresponding ejb-jar.xml:
{code:xml}
...
<session>
<ejb-name>StartupBean</ejb-name>
<session-type>Singleton</session-type>
<ejb-local-ref>
...
</ejb-local-ref>
</session>
{code}
Notice that the ejb-jar.xml is used to configure some other aspects of the EJB, but it
*doesn't* set/override the init-on-startup attribute of the bean. Effectively, the
StartupBean should still be considered as a init-on-startup bean.
However, this isn't the case currently. During merging of this annotation and xml
metadata, the merged metadata turns up the StartupBean as a normal non init-on-startup
bean. See the referenced forum thread for the complete details.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: