[
https://issues.apache.org/jira/browse/OPENJPA-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019958#comment-13019958
]
Michael Dick commented on OPENJPA-1977:
---------------------------------------
I think Rick is not proposing a behavior change (other than adding a message).
We'd still support final methods, but will treat them as constants which are
not persisted. From memory, the OpenJPA doc indicates such (but it's buried).
This wasn't obvious to at least a few users so a warning / info / trace message
that indicates what we're doing would be helpful.
A similar issue was reported on v1.0.1 in OPENJPA-465 - so this should be
consistent release to release. Tests to ensure it would be a nice bonus.
> 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
