[
https://issues.apache.org/jira/browse/OPENJPA-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679657#action_12679657
]
Jeremy Bauer commented on OPENJPA-932:
--------------------------------------
Comments on patch dated 2009-03-06 08:24 AM:
- I don't think a new trace group should be added specifically for this
warning. (OpenJPA trace groups are well documented in the manual, so if a new
group would need to be doc'd if consensus is that a new group should be
added.). While this exception shows up during enhancement, it is in product
derivation code so openjpa.Runtime may be better?
- I'm still struggling a bit with constructing a new config to get a logger,
but OpenJPA doesn't really have anything configured at this point and I can't
think of a cleaner way to get this important warning out there without other
potentially messy changes. The null check is good, IMHO. The comment
regarding its necessity can be removed.
- The error message isn't completely clear as to what the problem is or how to
fix it. I think wording which includes the notion that "persistence unit names
should be unique" may help. (I'd say must, but as this problem points out, we
don't enforce it)
> 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.
