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 Jencks (JIRA)" <ji...@apache.org> on 2011/06/18 07:01:47 UTC
[jira] [Created] (OPENEJB-1599) cmp-jpa code doesn't work well with
aries proxy weaving code
cmp-jpa code doesn't work well with aries proxy weaving code
------------------------------------------------------------
Key: OPENEJB-1599
URL: https://issues.apache.org/jira/browse/OPENEJB-1599
Project: OpenEJB
Issue Type: Bug
Components: cmp2
Affects Versions: 4.0-beta-1, 4.0
Reporter: David Jencks
Assignee: David Jencks
Fix For: 4.0-beta-1
The orm generator is finding the synthetic fields the aries proxy code adds and is listing them in the generated orm file. At least some of these are static and aren't found by the openjpa enhancer. These fields are all marked synthetic and it appears the openjpa knows enough to ignore synthetic fields so this can be fixed by having the orm generator ignore all synthetic fields.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (OPENEJB-1599) cmp-jpa code doesn't work well
with aries proxy weaving code
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENEJB-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks resolved OPENEJB-1599.
-----------------------------------
Resolution: Fixed
rev 1137123
> cmp-jpa code doesn't work well with aries proxy weaving code
> ------------------------------------------------------------
>
> Key: OPENEJB-1599
> URL: https://issues.apache.org/jira/browse/OPENEJB-1599
> Project: OpenEJB
> Issue Type: Bug
> Components: cmp2
> Affects Versions: 4.0-beta-1, 4.0
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 4.0-beta-1
>
>
> The orm generator is finding the synthetic fields the aries proxy code adds and is listing them in the generated orm file. At least some of these are static and aren't found by the openjpa enhancer. These fields are all marked synthetic and it appears the openjpa knows enough to ignore synthetic fields so this can be fixed by having the orm generator ignore all synthetic fields.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira