You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "David Blevins (JIRA)" <ji...@apache.org> on 2009/05/26 23:33:46 UTC
[jira] Updated: (OPENEJB-877) Allow pojo-style attributes in cmp2.x
beans as a migratiion path toward EJB3.
[ https://issues.apache.org/jira/browse/OPENEJB-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Blevins updated OPENEJB-877:
----------------------------------
Fix Version/s: (not version related)
Affects Version/s: (trunk/openejb3)
> Allow pojo-style attributes in cmp2.x beans as a migratiion path toward EJB3.
> -----------------------------------------------------------------------------
>
> Key: OPENEJB-877
> URL: https://issues.apache.org/jira/browse/OPENEJB-877
> Project: OpenEJB
> Issue Type: New Feature
> Components: cmp2
> Affects Versions: (trunk/openejb3)
> Reporter: Rick McGuire
> Assignee: Rick McGuire
> Fix For: (not version related)
>
>
> To assist migration from CMP 2.x beans to EJB3-style beans, it would be handy to allow a class to implement the CMP fields as concrete fields and classes in their code rather than requiring the methods to be abstract ones that are completed by the container system. This is something that JPA supports via mapped superclasses, so it should be possible to skip the code generation for the non-abstract methods and use the mapped-superclasses to enable these fields.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.