Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Date: Fri, 4 Mar 2011 17:49:37 +0000 (UTC)
From: "Craig L Russell (JIRA)" <jira@apache.org>
To: jdo-dev@db.apache.org
Message-ID: 
 <1204406791.14727.1299260977086.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1030071489.936.1298807098572.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Commented: (JDO-677) Ability to mark a class as read-only
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/JDO-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002743#comment-13002743 ] 

Craig L Russell commented on JDO-677:
-------------------------------------

So where would an error be identified? At the time the user modifies a persistent field? Or defer checking until flush (or commit)?

Portable behavior would probably mean defer checking.

Silently ignoring an update is probably not the right behavior.

> Ability to mark a class as read-only
> ------------------------------------
>
>                 Key: JDO-677
>                 URL: https://issues.apache.org/jira/browse/JDO-677
>             Project: JDO
>          Issue Type: New Feature
>          Components: api, specification, tck
>            Reporter: Andy Jefferson
>
> While JDO already allows a datastore to be marked as read-only (javax.jdo.option.ReadOnly), it would be desirable to extend this down to class-level. To achieve this we could add an (boolean) attribute "read-only" at class level to metadata. The same behaviour defined in the spec as for datastore-level would apply at class-level when a class is marked with this attribute as "true"

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira