OpenJPA
  1. OpenJPA
  2. OPENJPA-352

@Id annotation should be illegal when setter is missing

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 1.0.0
    • Fix Version/s: 2.0.0-M1, 2.0.0-M2, 2.0.0-M3
    • Component/s: jpa
    • Labels:
      None
    • Environment:
      Geronimo 2.0.1, Java 6

      Description

      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.

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Resolved Resolved
        774d 14h 46m 1 Pinaki Poddar 20/Oct/09 06:32
        Resolved Resolved Closed Closed
        140d 12h 58m 1 Donald Woods 09/Mar/10 18:31
        Donald Woods made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Pinaki Poddar made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Fix Version/s 2.0.0-M3 [ 12314148 ]
        Fix Version/s 2.0.0-M2 [ 12313483 ]
        Fix Version/s 2.0.0-M1 [ 12313624 ]
        Resolution Won't Fix [ 2 ]
        Hide
        Pinaki Poddar added a comment -

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

        Show
        Pinaki Poddar added a comment - An identity field can be generated. Hence a setXXX is not essential, in some cases even not recommended.
        Łukasz Budnik created issue -

          People

          • Assignee:
            Unassigned
            Reporter:
            Łukasz Budnik
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development