You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (Commented) (JIRA)" <ji...@apache.org> on 2012/01/05 18:52:39 UTC
[jira] [Commented] (ISIS-164) The validate() method should apply
for updates as well as for objects being initially persisted.
[ https://issues.apache.org/jira/browse/ISIS-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13180623#comment-13180623 ]
Dan Haywood commented on ISIS-164:
----------------------------------
This was originally raised as ISIS-18. Some fixes were made under ISIS-18 that addressed a related problem, but didn't actually address this problem. So have decided to clone ISIS-18 as this one, and update ISIS-18 to describe the issue that was addressed there.
> The validate() method should apply for updates as well as for objects being initially persisted.
> ------------------------------------------------------------------------------------------------
>
> Key: ISIS-164
> URL: https://issues.apache.org/jira/browse/ISIS-164
> Project: Isis
> Issue Type: Improvement
> Components: Runtimes: Dflt
> Affects Versions: 0.1.2-incubating
> Reporter: Dan Haywood
> Fix For: 0.3.0-incubating
>
>
> Currently the validate() method - used to check the overall state of an object, eg fromDate < toDate - only applies for an object that has just been created but not yet persisted.
> If an object is pulled back from the object store and then updated, the object-level validation is not re-run. For example that the fromDate could be modified > toDate; if there were no check in the modifyFromDate(), then the update would be allowed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira