[
https://issues.apache.org/jira/browse/TOMEE-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony M updated TOMEE-1664:
-----------------------------
Summary: CMP2JPA Conversion creates duplicate openejb-cmp-generated.xml
causing instability (was: CMP2JPA Conversion creates duplicate
openejn-cmp-generated.xml causing instability)
> CMP2JPA Conversion creates duplicate openejb-cmp-generated.xml causing
> instability
> ----------------------------------------------------------------------------------
>
> Key: TOMEE-1664
> URL: https://issues.apache.org/jira/browse/TOMEE-1664
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
> Affects Versions: 1.7.2
> Reporter: Anthony M
> Priority: Minor
> Labels: patch
>
> We are facing issues with the fact that the CMPJPAConversion code
> automatically generates/adds the mapping file openejb-cmp-generated-orm.xml
> to the CMP PeristenceUnit. Depending on startup either our custom version
> (defined inside of persistence.xml) or generated version takes precedence
> leading to inconsistent errors.
> I think the comment inside of CmpJpaConversion.java is stating as such " //
> todo scan existing persistence module for all entity mappings and don't
> generate mappings for them"
> Current work around was to rename the custom file to same name as
> "openejb-cmp-generated-orm.xml" AND remove mapping-file from our
> persistence.xml. The automatically generated file is the only file in the
> mappings list and our copy takes precedence due to classloader (the
> openejb.generated.jar seems to be added at end of classloader url list).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
