[ 
https://issues.apache.org/jira/browse/CAY-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dzmitry Kazimirchyk updated CAY-1616:
-------------------------------------

    Attachment: cross-context-mapping-strategy-unit-tests.patch
                cross-context-mappingstrategy-switching.patch
                cross-context-mapping-strategy-implementation.patch

Attaching implementation divided into 3 patches.

1. CrossContextMappingStrategy implementation for server and client.
2. Switching Cayenne to use the strategy instead of localObject().
3. Switching unit tests to strategy usage.
                
> Remove internal dependencies on deprecated ObjectContext.localObject
> --------------------------------------------------------------------
>
>                 Key: CAY-1616
>                 URL: https://issues.apache.org/jira/browse/CAY-1616
>             Project: Cayenne
>          Issue Type: Task
>          Components: Core Library
>    Affects Versions: 3.1M3
>            Reporter: Andrus Adamchik
>            Assignee: Andrus Adamchik
>         Attachments: cross-context-mapping-strategy-implementation.patch, 
> cross-context-mapping-strategy-unit-tests.patch, 
> cross-context-mappingstrategy-switching.patch
>
>
> CAY-1611 introduces user-facing API for obtaining context-local objects. 
> Still Cayenne internals keep using the old deprecated localObject(ObjectId, 
> Persistent) method in many places. We need to create a replacement. For a 
> replacement I am looking at binding a new DI service similar to this:
> CrossContextMappingStrategy
>    Persistent locateInContext(ObjectId id);
>    Persistent locateInChildContext(Persistent parentContextObject);
>    
> From there it will all be about figuring a way to inject 
> CrossContextMappingStrategy in various places where 'localObject' is used 
> currently. Also possibly BaseContext should use the first method for its 
> 'localObject' implementation.

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

        

Reply via email to