You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Marcel Offermans (JIRA)" <ji...@apache.org> on 2011/05/10 13:04:03 UTC

[jira] [Created] (FELIX-2947) Filter indices must use service trackers that track all services and aspects.

Filter indices must use service trackers that track all services and aspects.
-----------------------------------------------------------------------------

                 Key: FELIX-2947
                 URL: https://issues.apache.org/jira/browse/FELIX-2947
             Project: Felix
          Issue Type: Improvement
          Components: Dependency Manager
    Affects Versions: dependencymanager-3.0.0
            Reporter: Marcel Offermans


Both current implementations of filter indices use a service tracker that listens to all services to keep their index in sync with the service registry. However, the current service tracker tries to be smart when it comes to aspects and hides aspects and services with a lower ranking so all but the highest is visible. Whilst this logic is desirable for components that depend on certain services, it is undesirable for an index. We were especially seeing problems when services with multiple interfaces had aspects on one of their interfaces.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (FELIX-2947) Filter indices must use service trackers that track all services and aspects.

Posted by "Marcel Offermans (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Offermans resolved FELIX-2947.
-------------------------------------

    Resolution: Fixed

Issue fixed after using the modified service tracker as mentioned in FELIX-2946.

> Filter indices must use service trackers that track all services and aspects.
> -----------------------------------------------------------------------------
>
>                 Key: FELIX-2947
>                 URL: https://issues.apache.org/jira/browse/FELIX-2947
>             Project: Felix
>          Issue Type: Improvement
>          Components: Dependency Manager
>    Affects Versions: dependencymanager-3.0.0
>            Reporter: Marcel Offermans
>            Assignee: Marcel Offermans
>
> Both current implementations of filter indices use a service tracker that listens to all services to keep their index in sync with the service registry. However, the current service tracker tries to be smart when it comes to aspects and hides aspects and services with a lower ranking so all but the highest is visible. Whilst this logic is desirable for components that depend on certain services, it is undesirable for an index. We were especially seeing problems when services with multiple interfaces had aspects on one of their interfaces.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Assigned] (FELIX-2947) Filter indices must use service trackers that track all services and aspects.

Posted by "Marcel Offermans (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Offermans reassigned FELIX-2947:
---------------------------------------

    Assignee: Marcel Offermans

> Filter indices must use service trackers that track all services and aspects.
> -----------------------------------------------------------------------------
>
>                 Key: FELIX-2947
>                 URL: https://issues.apache.org/jira/browse/FELIX-2947
>             Project: Felix
>          Issue Type: Improvement
>          Components: Dependency Manager
>    Affects Versions: dependencymanager-3.0.0
>            Reporter: Marcel Offermans
>            Assignee: Marcel Offermans
>
> Both current implementations of filter indices use a service tracker that listens to all services to keep their index in sync with the service registry. However, the current service tracker tries to be smart when it comes to aspects and hides aspects and services with a lower ranking so all but the highest is visible. Whilst this logic is desirable for components that depend on certain services, it is undesirable for an index. We were especially seeing problems when services with multiple interfaces had aspects on one of their interfaces.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira