cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrus Adamchik (Updated) (JIRA)" <>
Subject [jira] [Updated] (CAY-1625) Transient objects do not work in ROP apps
Date Tue, 06 Dec 2011 03:35:41 GMT


Andrus Adamchik updated CAY-1625:

    Attachment: 0001-CAY-1625-Transient-objects-do-not-work-in-ROP-apps.patch

Attaching a reworked patch based on John's. Changes:

1. Undid some new formatting so that the actual logic changes are more clear.

2. Removed an additional strategy change not directly related to handling of transients -
the 'safeEquals' check. This is not necessarily wrong, just an unrelated aspect requiring
its own discussion.

I am not applying the patch yet, as we'll need to ensure that all our client test cases are
switched to the new format and all the tests pass. Anybody feel free to perform this work
and create an extra patch here.
> Transient objects do not work in ROP apps
> -----------------------------------------
>                 Key: CAY-1625
>                 URL:
>             Project: Cayenne
>          Issue Type: Improvement
>          Components: ROP
>    Affects Versions: 3.1M4
>         Environment: Mac 10.6
>            Reporter: John Huss
>            Priority: Minor
>              Labels: patch
>         Attachments: 0001-CAY-1625-Transient-objects-do-not-work-in-ROP-apps.patch, revised
client template transient.txt
>   Original Estimate: 72h
>  Remaining Estimate: 72h
> In addition the problem referenced in CAY-1624, transient objects don't work when using
ROP because in the client template the relationship values (to-one and to-many) are   null
and are only initialized to non-null values when they are added to an ObjectContext.  By modifying
the template to initialize the relationship values to something non-null, transient objects
can be worked with locally (but not still saved?).  I don't know if that is the best solution,
but here's basically what I did.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message