[
https://issues.apache.org/jira/browse/OPENJPA-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679652#action_12679652
]
Michael Dick commented on OPENJPA-932:
--------------------------------------
Hi Rick,
The current patch will *always* log to StdErr. I think we'd be better off
saving the fact that there was a name collision and logging it after we've
parsed the configuration.
I'm also not sure we need a new logging level for this issue. Wouldn't one of
the other levels, ie Runtime have sufficed?
> Runtime enhancer doesn't work propery if there is a trailing persistence.xml
> file on the classpath.
> ---------------------------------------------------------------------------------------------------
>
> Key: OPENJPA-932
> URL: https://issues.apache.org/jira/browse/OPENJPA-932
> Project: OpenJPA
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.2.0, 2.0.0-M1, 2.0.0
> Reporter: Rick Curtis
> Attachments: OPENJPA-932-2.0.patch
>
>
> I have an application where I am using runtime class enhancement via the
> javaagent and I set openjpa.RuntimeUnenhancedClasses=unsupported. My
> application works fine when running on 1.1.0 but when I moved to 1.2.0 (and
> 2.0.0) I started getting errors because my classes aren't being enhanced.
> After debugging I determined that I had a jar on the end of my classpath that
> had a META-INF/persistence.xml file in it. The extra persistence.xml file has
> no PUs defined, and should have been ignored. When I removed that jar from my
> classpath things starting working again. It also works if I put my
> META-INF/persistence.xml file on the end of my classpath.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
