You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2015/01/03 16:06:34 UTC
[jira] [Comment Edited] (ISIS-755) Allow external system data to be
integrated and managed with an Apache Isis domain object
[ https://issues.apache.org/jira/browse/ISIS-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14064885#comment-14064885 ]
Dan Haywood edited comment on ISIS-755 at 1/3/15 3:05 PM:
----------------------------------------------------------
David,
Just catching up on this ticket.
I think your original list of requirements are a pretty tall order. Not that they are necessarily unreasonable, but they are difficult to implement, and would require Isis to retain a lot of the ORM functionality that it currently has within it for the non-JDO object stores.
In your own comment on this ticket, though, it seems that your "potential solution" - which also makes sense to me - basically means that in actual fact there's no requirement to do anything in the framework at all; rather this becomes something that is addressed through the design of the app itself.
If you're still happy with that original potential solution you sketched out, then I think that this ticket basically amounts to just documenting the solution on the website somewhere; no new coding needed.
Can you reply on this ticket for traceability?
Thx
Dan
was (Author: danhaywood):
David,
Just catching up on this ticket.
I think your original list of requirements are a pretty tall order. Not that they are necessarily unreasonable, but they are difficult to implement, and would require Isis to retain a lot of the ORM functionality that it currently has within it for the non-JDO object stores.
In your own comment on this ticket, though, it seems that your "potential solution" - which also makes sense to me - basically means that in actual fact there's no requirement to do anything in the framework at all; rather this becomes something that is addressed through the design of the app itself.
If you're still happy with that original potential solution you sketched out, then I think that this ticket basically amounts to just documenting the solution on the website somewhere; no codes needed.
Can you reply on this ticket for traceability?
Thx
Dan
> Allow external system data to be integrated and managed with an Apache 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.8.0
>
>
> 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.3.4#6332)