[
https://issues.apache.org/jira/browse/ISIS-743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13940288#comment-13940288
]
David Tildesley edited comment on ISIS-743 at 3/19/14 8:25 AM:
---------------------------------------------------------------
Not really (fears remain). Anything can be an "oid" for a domain object - it
doesn't have to be a persisted object identifier (that you would get
automatically via the DM). e.g it could be an employee number, social security
number, acccount number ... which would typically be the case if the
information was coming from an external service. I can see you would have an
immediate problem with this with a generated viewer - so I would need to give
it some thought.
Using JDO with a custom plugged in persistence implementation appears way too
complex to me. Bypassing the PD layer ( i.e. UI <-- SI) is promoting shifting
business logic into the UI layer. Both unpalatable. By the way I am assuming
the domain service is pretty much the equivalent of a System Integration layer
(takes care of the marshalling and unmarshalling of data to and from some
service integration and connected to the domain object via DI.
This old but relevant thread is worth reading [1]
[1] http://www.featuredrivendevelopment.com/node/582
was (Author: davotnz):
Not really (fears remain). Anything can be an "oid" for a domain object - it
doesn't have to be a persisted object identifier (that you would get
automatically via the DM). e.g it could be an employee number, social security
number, acccount number ... which would typically be the case of the
information was coming from an external service. I can see you would have an
immediate problem with this with a generated viewer - so I would need to give
it some thought.
Using JDO with a custom plugged in persistence implementation appears way too
complex to me. Bypassing the PD layer ( i.e. UI <-- SI) is promoting shifting
business logic into the UI layer. Both unpalatable. By the way I am assuming
the domain service is pretty much the equivalent of a System Integration layer
(takes care of the marshalling and unmarshalling of data to and from some
service integration and connected to the domain object via DI.
This old but relevant thread is worth reading [1]
[1] http://www.featuredrivendevelopment.com/node/582
> Remove the concept of transient objects and of @NotPersistable; instead we
> have view models.
> --------------------------------------------------------------------------------------------
>
> Key: ISIS-743
> URL: https://issues.apache.org/jira/browse/ISIS-743
> Project: Isis
> Issue Type: Wish
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: core-2.0.0
>
> Attachments: Design-1.PNG, Design-2.PNG
>
>
> For discussion; but think that view models supercede our earlier ideas of
> transient objects etc.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
