[jira] [Resolved] (TORQUE-343) Implement a central registry for peerImpls like the registry for managers

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jira] [Resolved] (TORQUE-343) Implement a central registry for peerImpls like the registry for managers

JIRA jira@apache.org

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

Thomas Vandahl resolved TORQUE-343.
-----------------------------------
    Resolution: Fixed

> Implement a central registry for peerImpls like the registry for managers
> -------------------------------------------------------------------------
>
>                 Key: TORQUE-343
>                 URL: https://issues.apache.org/jira/browse/TORQUE-343
>             Project: Torque
>          Issue Type: Improvement
>          Components: Runtime, Templates
>    Affects Versions: 4.0
>            Reporter: Thomas Vandahl
>            Assignee: Thomas Vandahl
>             Fix For: 4.1
>
>
> I'd like to suggest a central registry for peerImpl-objects which can be queried by the Persistent class it is responsible for. This would allow reusing and extending the peer objects dynamically as well as giving them some kind of life-cycle.
> The main method would be similar to this:
> {code:java}
> public <T> BasePeerImpl<T> getPeerFor(Class<T> persistentClass)
> {
>     return peerRegistry.get(persistentClass);
> }
> {code}
> I would also like to suggest moving the buildCriteria(obj) method to the RecordMapper or the TableMap class. This will further reduce the amount of code that needs to be generated.
> If the idea is received well, I'll come up with a proposal.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Loading...