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 (JIRA)" <ji...@apache.org> on 2010/12/13 12:54:01 UTC

[jira] Created: (ISIS-18) The validate() method should apply for updates as well as for objects being initially persisted.

The validate() method should apply for updates as well as for objects being initially persisted.
------------------------------------------------------------------------------------------------

                 Key: ISIS-18
                 URL: https://issues.apache.org/jira/browse/ISIS-18
             Project: Isis
          Issue Type: Improvement
          Components: Core: Runtime
            Reporter: Dan Haywood


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.
-
You can reply to this email to add a comment to the issue online.


[jira] [Closed] (ISIS-18) DateParser error under de_DE.

Posted by "Dan Haywood (Closed) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ISIS-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Haywood closed ISIS-18.
---------------------------

    
> DateParser error under de_DE.
> -----------------------------
>
>                 Key: ISIS-18
>                 URL: https://issues.apache.org/jira/browse/ISIS-18
>             Project: Isis
>          Issue Type: Bug
>          Components: Runtimes: Dflt
>    Affects Versions: 0.1.2-incubating
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>            Priority: Minor
>             Fix For: 0.2.0-incubating
>
>
> Originally this ticket was to cover the issue now described by ISIS-164.  However, fixes were made under this ticket that addressed a related problem (see commit messages), but didn't actually address the original problem in ISIS-164.  So have decided to update this issue to describe the issue that was addressed there.

--
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

        

[jira] [Updated] (ISIS-18) DateParser error under de_DE.

Posted by "Dan Haywood (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ISIS-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Haywood updated ISIS-18:
----------------------------

    Description: 
Originally this ticket was to cover the issue now described by ISIS-164.  However, fixes were made under this ticket that addressed a related problem (see commit messages), but didn't actually address the original problem in ISIS-164.  So have decided to update this issue to describe the issue that was addressed there.



  was:
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.

       Priority: Minor  (was: Major)
     Issue Type: Bug  (was: Improvement)
        Summary: DateParser error under de_DE.  (was: The validate() method should apply for updates as well as for objects being initially persisted.)
    
> DateParser error under de_DE.
> -----------------------------
>
>                 Key: ISIS-18
>                 URL: https://issues.apache.org/jira/browse/ISIS-18
>             Project: Isis
>          Issue Type: Bug
>          Components: Runtimes: Dflt
>    Affects Versions: 0.1.2-incubating
>            Reporter: Dan Haywood
>            Priority: Minor
>             Fix For: 0.2.0-incubating
>
>
> Originally this ticket was to cover the issue now described by ISIS-164.  However, fixes were made under this ticket that addressed a related problem (see commit messages), but didn't actually address the original problem in ISIS-164.  So have decided to update this issue to describe the issue that was addressed there.

--
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

        

[jira] [Resolved] (ISIS-18) DateParser error under de_DE.

Posted by "Dan Haywood (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ISIS-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Haywood resolved ISIS-18.
-----------------------------

    Resolution: Fixed
      Assignee: Dan Haywood
    
> DateParser error under de_DE.
> -----------------------------
>
>                 Key: ISIS-18
>                 URL: https://issues.apache.org/jira/browse/ISIS-18
>             Project: Isis
>          Issue Type: Bug
>          Components: Runtimes: Dflt
>    Affects Versions: 0.1.2-incubating
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>            Priority: Minor
>             Fix For: 0.2.0-incubating
>
>
> Originally this ticket was to cover the issue now described by ISIS-164.  However, fixes were made under this ticket that addressed a related problem (see commit messages), but didn't actually address the original problem in ISIS-164.  So have decided to update this issue to describe the issue that was addressed there.

--
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

        

[jira] [Updated] (ISIS-18) The validate() method should apply for updates as well as for objects being initially persisted.

Posted by "Dan Haywood (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ISIS-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Haywood updated ISIS-18:
----------------------------

    Affects Version/s: 0.1.2-incubating
    
> The validate() method should apply for updates as well as for objects being initially persisted.
> ------------------------------------------------------------------------------------------------
>
>                 Key: ISIS-18
>                 URL: https://issues.apache.org/jira/browse/ISIS-18
>             Project: Isis
>          Issue Type: Improvement
>          Components: Runtimes: Dflt
>    Affects Versions: 0.1.2-incubating
>            Reporter: Dan Haywood
>             Fix For: 0.2.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