[
https://issues.apache.org/jira/browse/POLYGENE-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niclas Hedhman updated POLYGENE-288:
------------------------------------
Description:
We have a huge set of places where a hook is executed outside the Core Runtime.
We are detecting some anomalies and we have for a long time struggled with
getting the semantics correct for Initializable, Lifecycle and Activation.
I want to suggest that we identify ALL possible hooks in existence and design
mechanism to easily add a new implementation of a hook. In many cases, we have
succeeded in this by extracting Runtime parts out to become Composites, which
are easily replaced. And possibly a lot of this work is to make those composite
more extension-friendly, by breaking out the 'hook' as a method call that can
be intercepted or replaced. This may or may not be enough to cover all (or at
least majority of cases).
I suggest that each HOOK is created as an independent JIRA issue, that has
"MetaHook -" in the name and "is a child of" dependency back to this issue.
was:
We have a huge set of places where a hook is executed outside the Core Runtime.
We are detecting some anomalies and we have for a long time struggled with
getting the semantics correct for Initializable, Lifecycle and Activation.
I want to suggest that we identify ALL possible hooks in existence and design
mechanism to easily add a new implementation of a hook. In many cases, we have
succeeded in this by extracting Runtime parts out to become Composites, which
are easily replaced. And possibly a lot of this work is to make those composite
more extension-friendly, by breaking out the 'hook' as a method call that can
be intercepted or replaced. This may or may not be enough to cover all (or at
least majority of cases).
I suggest that each HOOK is created as an independent JIRA issue, that has a
"is a child of" dependency back to this issue.
> MetaHook - Refactor Core Runtime hooks
> --------------------------------------
>
> Key: POLYGENE-288
> URL: https://issues.apache.org/jira/browse/POLYGENE-288
> Project: Polygene
> Issue Type: New Feature
> Reporter: Niclas Hedhman
>
> We have a huge set of places where a hook is executed outside the Core
> Runtime. We are detecting some anomalies and we have for a long time
> struggled with getting the semantics correct for Initializable, Lifecycle and
> Activation.
> I want to suggest that we identify ALL possible hooks in existence and design
> mechanism to easily add a new implementation of a hook. In many cases, we
> have succeeded in this by extracting Runtime parts out to become Composites,
> which are easily replaced. And possibly a lot of this work is to make those
> composite more extension-friendly, by breaking out the 'hook' as a method
> call that can be intercepted or replaced. This may or may not be enough to
> cover all (or at least majority of cases).
> I suggest that each HOOK is created as an independent JIRA issue, that has
> "MetaHook -" in the name and "is a child of" dependency back to this issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
