[
https://issues.apache.org/jira/browse/ISIS-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13943988#comment-13943988
]
Dan Haywood commented on ISIS-755:
----------------------------------
You might already know that there are some hooks already, as per [1]. So this
ticket might then amount to little more than confirming that those hooks are
called reliably in every circumstance (in particular, lazy loading)
One downside of this design is that it would give rise to the N+1 problem that
afflicts ORMs... a single query to obtain locally persisted objects, then N
calls to a remote store to hydrate with externally-handled data. So an
enhancement might be hook into the querying and do a single remote query also,
then do injection of remote state in bulk to all objects being returned by the
query.
[1]
http://isis.apache.org/more-advanced-topics/how-to-07-020-How-to-insert-behaviour-into-the-object-life-cycle.html
> Allow external system data to be integrated and managed with an ISIS domain
> object
> -----------------------------------------------------------------------------------
>
> Key: ISIS-755
> URL: https://issues.apache.org/jira/browse/ISIS-755
> Project: Isis
> Issue Type: Improvement
> Components: Core
> Affects Versions: core-1.4.0
> Reporter: David Tildesley
> Assignee: Dan Haywood
> Fix For: core-1.4.2
>
>
> Problem statement: The framework currently offers no lifecycle support for
> domain objects that get their data from and to external systems.
> Requirements:
> 1. Manage domain object state lifecycle consistent with a locally persisted
> domain object.
> 2. Treat the domain object as a peer with all other domain objects for viewer
> generation and integration.
> 3. Integrate with standard OTB domain services such as audit service.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
