openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pinaki Poddar (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (OPENJPA-352) @Id annotation should be illegal when setter is missing
Date Tue, 20 Oct 2009 05:32:59 GMT

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

Pinaki Poddar resolved OPENJPA-352.
-----------------------------------

       Resolution: Won't Fix
    Fix Version/s: 2.0.0-M1
                   2.0.0-M2
                   2.0.0-M3

An identity field can be generated. Hence a setXXX is not essential, in some cases even not
recommended.

> @Id annotation should be illegal when setter is missing
> -------------------------------------------------------
>
>                 Key: OPENJPA-352
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-352
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jpa
>    Affects Versions: 1.0.0
>         Environment: Geronimo 2.0.1, Java 6
>            Reporter: Ɓukasz Budnik
>             Fix For: 2.0.0-M3, 2.0.0-M2, 2.0.0-M1
>
>
> The @Id annotation on the getXXX method  is illegal when there is no corresponding setXXX
method.
> OpenJPA allows such cases when it should rise an error.

-- 
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