openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Albert Lee (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (OPENJPA-565) Duplicate @NamedQuery terminates subsequent @NameQuery definitions in @NamedQueries
Date Fri, 11 Apr 2008 14:46:04 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Albert Lee resolved OPENJPA-565.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2.0

> Duplicate @NamedQuery terminates subsequent @NameQuery definitions in @NamedQueries 
> ------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-565
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-565
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 1.0.2, 1.0.3, 1.1.0
>            Reporter: Albert Lee
>            Assignee: Albert Lee
>            Priority: Minor
>             Fix For: 1.0.3, 1.1.0, 1.2.0
>
>
> If duplicate @NameQuery is defined in @NameQueries as in, 
> @NamedQueries (
>   {  @NamedQuery(name="findBasicAByBasicBid", query="select t.entitya from BasicB t WHERE
t.id = ?1" ),
>      @NamedQuery(name="findBasicAByBasicBid", query="select t.entitya from BasicB t WHERE
t.id = ?1"),
>      @NamedQuery(name="findInhAddress",	query="select t from InhAddress t)
> })
> a warning  message is posted in the log
> openjpa.MetaData - Found duplicate query "findBasicAByBasicBid" in "class com.ibm.ws.query.pdq.entities.TypeTestBean".
 Ignoring.
> Although the message said the query is ignored, it actually terminates the detection
of the remaining NamedQuery definitions.
> Albert Lee.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message