You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Rick Curtis (Commented) (JIRA)" <ji...@apache.org> on 2012/02/14 15:31:59 UTC

[jira] [Commented] (OPENJPA-2129) Getting WARN messages [main] openjpa.MetaData - Found duplicate metadata or mapping for "class xxx.xxx". Ignoring.

    [ https://issues.apache.org/jira/browse/OPENJPA-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13207737#comment-13207737 ] 

Rick Curtis commented on OPENJPA-2129:
--------------------------------------

> It is not able to execute actual code.
Please elaborate. What happened? 

> It seems there is a bug. Please look into this issue and fix it or suggest alternative solution as soon as possible. 
Again, you're going to need to provide more information to help us understand what is happening. 

Is this a JSE or JEE test? How are you enhancing your Entities? Can you provide a simple test to recreate the issue?
                
> Getting WARN messages [main] openjpa.MetaData - Found duplicate metadata or mapping for "class xxx.xxx".  Ignoring.
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-2129
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2129
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jpa
>    Affects Versions: 2.1.1
>            Reporter: aabbcc
>
> I am trying to execute Junit test for ORM mapping using OPENJPA2.1.1
> Getting below Duplicate OpenJPA meta data warning     
> [main] openjpa.MetaData - Found duplicate metadata or mapping for "class xxx.xxx".  Ignoring.
> It is not able to execute actual code. There are no two mapping files with same content. It seems OpenJPA parsing the same orm.xml location twice.
> It seems there is a bug. Please look into this issue and fix it or suggest alternative solution as soon as possible.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira