You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jdo-dev@db.apache.org by "Chris Beams (JIRA)" <ji...@apache.org> on 2007/10/05 19:36:50 UTC

[jira] Assigned: (JDO-540) Support for final modifier on fields of Persistence-Capable classes

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

Chris Beams reassigned JDO-540:
-------------------------------

    Assignee: Chris Beams

Action Item for Chris to look deeper into the implementation issues.

At this point, the cost/benefit ratio looks pretty high for adding this feature.  Perhaps it's justifiable after some research.  We'll see...

> Support for final modifier on fields of Persistence-Capable classes
> -------------------------------------------------------------------
>
>                 Key: JDO-540
>                 URL: https://issues.apache.org/jira/browse/JDO-540
>             Project: JDO
>          Issue Type: New Feature
>          Components: api2
>            Reporter: Chris Beams
>            Assignee: Chris Beams
>             Fix For: JDO 2 maintenance release 1
>
>
> Per changes introduced in Java5 as part of JSR-133, post-construction modification of final fields is now possible when calling setAccessible(true) on a field via reflection.
> Heinz Kabutz gives a good discussion of the feature: http://www.javaspecialists.eu/archive/Issue096.html
> Supporting final on fields would make JDO even less intrusive than it already is, and would allow users to create richer class definitions.
> Let's discuss...

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