[
https://issues.apache.org/jira/browse/JDO-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006158#comment-13006158
]
Andy Jefferson commented on JDO-677:
------------------------------------
I'd place checking at the point the data is about to be sent to the datastore
... if using datastore txns then this may be immediately, and if using
optimistic txns then this will be at flush/commit. In both cases a
JDOReadOnlyException is the required result.
> 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
