[
https://issues.apache.org/jira/browse/ISIS-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14030708#comment-14030708
]
Dan Haywood commented on ISIS-803:
----------------------------------
Oscar's point:
We cannot impede that a user use the JDO or JPA standard methods. So, despite
they are a not good practice, we at least should "support" when the standard
JDO (JPA in the future) lifecycle methods are used (i.e., by "detecting" the
changes on those domain objects, if that's used by Isis; but not sure if
there's something special to do by Isis).
Dan said:
fair enough; we can't unilaterally withdraw features, I suppose. This ticket
was about Isis' own lifecycle methods.
> Replace lifecycle methods with additional EventBus events.
> ----------------------------------------------------------
>
> Key: ISIS-803
> URL: https://issues.apache.org/jira/browse/ISIS-803
> Project: Isis
> Issue Type: Improvement
> Components: Core
> Affects Versions: core-1.5.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: core-2.0.0
>
>
> This issue is to remove a feature that is only partly implemented in the JDO
> objectstore, namely the lifecycle methods.
> Jeroen and I were discussing this, and think they are possibly an
> anti-pattern since they tend to lead to fragile code.
> Rather than have the object "pushing" changes to others, it would be better
> if an event were broadcast via the EventBus. That way a subscribing service
> could pull appropriate changes and do whatever is necessary.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
