You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2009/08/03 11:29:16 UTC
[jira] Created: (FELIX-1443) Unify Method lookup
Unify Method lookup
-------------------
Key: FELIX-1443
URL: https://issues.apache.org/jira/browse/FELIX-1443
Project: Felix
Issue Type: Improvement
Components: Declarative Services (SCR)
Affects Versions: scr-1.2.0
Reporter: Felix Meschberger
Assignee: Felix Meschberger
Fix For: scr-1.2.0
Currently method lookup for activator and for bind methods is similar but indication of whether a method is found or not is completely different: (de)activator method indication is based on a sentinel method while (un)bind method indication is based on an internal state machine and an object representing the method to be looked up and called.
It would be good to unify the two approaches to get a single one. FInd details of method selection remain disctinct due to different requirements for method signatures. But maybe some coercion is also possible on that level.
Looking at the current two approaches, the new (un)bind method approach (provided as part of FELIX-924 by Alin Dreghiciu) with a Facade class for method lookup and invocation looks very promising and might be the base for this coercion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1443) Unify Method lookup
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed FELIX-1443.
------------------------------------
SCR 1.2.0 has been released. Close all issues.
> Unify Method lookup
> -------------------
>
> Key: FELIX-1443
> URL: https://issues.apache.org/jira/browse/FELIX-1443
> Project: Felix
> Issue Type: Improvement
> Components: Declarative Services (SCR)
> Affects Versions: scr-1.2.0
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: scr-1.2.0
>
>
> Currently method lookup for activator and for bind methods is similar but indication of whether a method is found or not is completely different: (de)activator method indication is based on a sentinel method while (un)bind method indication is based on an internal state machine and an object representing the method to be looked up and called.
> It would be good to unify the two approaches to get a single one. FInd details of method selection remain disctinct due to different requirements for method signatures. But maybe some coercion is also possible on that level.
> Looking at the current two approaches, the new (un)bind method approach (provided as part of FELIX-924 by Alin Dreghiciu) with a Facade class for method lookup and invocation looks very promising and might be the base for this coercion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-1443) Unify Method lookup
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger resolved FELIX-1443.
--------------------------------------
Resolution: Fixed
Implemented the big refactoring in Rev. 800496.
We now have a BaseMethod providing the basis for method resolution and invocation and we have extensions for various method support like activate, deactivate, modified, bind, and unbind.
> Unify Method lookup
> -------------------
>
> Key: FELIX-1443
> URL: https://issues.apache.org/jira/browse/FELIX-1443
> Project: Felix
> Issue Type: Improvement
> Components: Declarative Services (SCR)
> Affects Versions: scr-1.2.0
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: scr-1.2.0
>
>
> Currently method lookup for activator and for bind methods is similar but indication of whether a method is found or not is completely different: (de)activator method indication is based on a sentinel method while (un)bind method indication is based on an internal state machine and an object representing the method to be looked up and called.
> It would be good to unify the two approaches to get a single one. FInd details of method selection remain disctinct due to different requirements for method signatures. But maybe some coercion is also possible on that level.
> Looking at the current two approaches, the new (un)bind method approach (provided as part of FELIX-924 by Alin Dreghiciu) with a Facade class for method lookup and invocation looks very promising and might be the base for this coercion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.