[
https://issues.apache.org/jira/browse/OPENJPA-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019385#comment-13019385
]
Milosz Tylenda commented on OPENJPA-1977:
-----------------------------------------
Hi Rick. My thought is that it is not obvious how to read the JPA spec. I would
read it that it is not forbidden for an implementation to support entities with
final methods. Such an entity would just not be an entity in JPA terms but an
"OpenJPA entity" (with some analogy to OpenJPA managed interfaces). So, ideally
we could support final methods, maybe thru a switch and with warning.
I am OK with both updating the docs to reflect the reality or introducing
(re-introducing?) handling of final methods if someone is willing to. Would be
interesting to see how an OpenJPA version < 1.0 behaves in this area.
> Final methods are not supported but documentation sais they are
> ---------------------------------------------------------------
>
> Key: OPENJPA-1977
> URL: https://issues.apache.org/jira/browse/OPENJPA-1977
> Project: OpenJPA
> Issue Type: Bug
> Components: jpa
> Affects Versions: 2.1.0
> Reporter: Heinz Striebeck
> Assignee: Rick Curtis
> Priority: Minor
>
> See
> http://openjpa.208410.n2.nabble.com/Issues-with-GeneratedValue-and-SequenceGenerator-td6244055.html
> When using final methods for the id field, the generated id is unavailable
> for the application.
> According to the mailing list, final methods are not supported, but the
> OpenJPA documentation sais so:
> http://openjpa.apache.org/builds/2.1.0/apache-openjpa-2.1.0/docs/manual/jpa_overview_pc.html#jpa_overview_pc_final
> So at least the documentation should be changed.
> An error message at runtime would also be fine - that would be also related to
> https://issues.apache.org/jira/browse/OPENJPA-465
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
