[OS-JIRA] Created: (CAY-380) localObjects() throws exception on MODIFIED objects

From: jira-norepl..bjectstyle.org
Date: Fri Sep 23 2005 - 13:47:38 EDT

  • Next message: Mike Kienenberger: "Re: SCM Repository"

    Message:

      A new issue has been created in JIRA.

    ---------------------------------------------------------------------
    View the issue:

      http://objectstyle.org/jira/secure/ViewIssue.jspa?key=CAY-380

    Here is an overview of the issue:
    ---------------------------------------------------------------------
            Key: CAY-380
        Summary: localObjects() throws exception on MODIFIED objects
           Type: Improvement

         Status: Assigned
       Priority: Major

        Project: Cayenne
     Components:
                 Cayenne Core Library
       Versions:
                 1.2 [DEV]

       Assignee: Andrus Adamchik
       Reporter: Mike Kienenberger

        Created: Fri, 23 Sep 2005 1:46 PM
        Updated: Fri, 23 Sep 2005 1:46 PM

    Description:
    On Jan 19, 2005, at 2:40 PM, Mike Kienenberger wrote:
    > Is there a reason why a MODIFIED object couldn't be copied into a
    > new context?

    Andrus Adamchik <andru..bjectstyle.org> wrote:
    ] I agree - current behavior (throwing an exception) is probably not
    ] the best solution... I am in favor of changing that... The question
    ] is - do we want to copy a changed object, or a committed version of
    ] it? To be on a safe side, I'd say committed (but maybe there are
    ] valid cases for copying the changes as well?)

    Mike Kienenberger wrote:
    > I would say that the modified values should be copied.
    > That would be the behavior end-users expect. It was the behavior
    > that Andre expected.

    Andrus Adamchik <andru..bjectstyle.org> wrote:
    ] Makes sense. It's fine with me.

    Mike Kienenberger wrote:
    > It'd require a new method call in localObjects to copy a DataObject.
    > We've
    > seen a number of requests to copy DataObjects pop up in the past on
    > the user
    > list, and I can't help but wonder if perhaps the ability to clone a
    > DataObject should be added to DataObjectUtils (or even to DataObject
    > itself).

    Andrus Adamchik <andru..bjectstyle.org> wrote:
    ] And with the whole POJO discussion this may become even more
    ] important... And I'd say copying not just a set of objects but a
    ] specified relationships as well, i.e. a piece of object graph. I am
    ] for adding this to DataObjectUtils for now, as I really hate to
    ] expand DataObject further until we settle on the whole POJO
    ] direction.

    ---------------------------------------------------------------------
    JIRA INFORMATION:
    This message is automatically generated by JIRA.

    If you think it was sent incorrectly contact one of the administrators:
       http://objectstyle.org/jira/secure/Administrators.jspa

    If you want more information on JIRA, or have a bug to report see:
       http://www.atlassian.com/software/jira



    This archive was generated by hypermail 2.0.0 : Fri Sep 23 2005 - 13:47:40 EDT