[jboss-jira] [JBoss JIRA] Resolved: (JBMETA-275) Allow the session bean metadata created out of jboss 5.0 and 5.1 to be used for EJB3.1 beans
jaikiran pai (JIRA)
jira-events at lists.jboss.org
Mon Apr 5 05:03:37 EDT 2010
[ https://jira.jboss.org/jira/browse/JBMETA-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
jaikiran pai resolved JBMETA-275.
---------------------------------
Fix Version/s: jboss-metadata-ejb-2.0.0-alpha-10
Resolution: Done
> Allow the session bean metadata created out of jboss 5.0 and 5.1 to be used for EJB3.1 beans
> --------------------------------------------------------------------------------------------
>
> Key: JBMETA-275
> URL: https://jira.jboss.org/jira/browse/JBMETA-275
> Project: JBoss Metadata
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: ejb
> Affects Versions: jboss-metadata-ejb-2.0.0-alpha-9
> Reporter: jaikiran pai
> Assignee: jaikiran pai
> Fix For: jboss-metadata-ejb-2.0.0-alpha-10
>
>
> When metadata is created out of jboss.xml with 5.0 and 5.1 xsd, they respectively create JBoss50SessionBeanMetaData and JBoss51SessionBeanMetaData objects. Both these classes extend from JBossSessionBeanMetaData which effectively means that they won't be considered EJB3.1 session beans (even if the corresponding ejb-jar.xml marks them as 3.1 beans through its xsd).
> To allow these 2 jboss xsds to be used against EJB3.1 beans, let them extend from JBossSessionBean31MetaData
--
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
More information about the jboss-jira
mailing list