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 2007/10/01 11:30:50 UTC

[jira] Created: (FELIX-385) ReferenceMetadata.setTarget includes the interface name in the target filter

ReferenceMetadata.setTarget includes the interface name in the target filter
----------------------------------------------------------------------------

                 Key: FELIX-385
                 URL: https://issues.apache.org/jira/browse/FELIX-385
             Project: Felix
          Issue Type: Bug
          Components: Declarative Services
            Reporter: Felix Meschberger
            Assignee: Felix Meschberger
             Fix For: 1.0.0


When the target filter is set on a reference metadata, the interface name is included as a filter term. This is not required as the service access primarily uses the interface directly and service listener registration adds the interface to the target filter, if existing, anyway.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Work started: (FELIX-385) ReferenceMetadata.setTarget includes the interface name in the target filter

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

Work on FELIX-385 started by Felix Meschberger.

> ReferenceMetadata.setTarget includes the interface name in the target filter
> ----------------------------------------------------------------------------
>
>                 Key: FELIX-385
>                 URL: https://issues.apache.org/jira/browse/FELIX-385
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: 1.0.0
>
>
> When the target filter is set on a reference metadata, the interface name is included as a filter term. This is not required as the service access primarily uses the interface directly and service listener registration adds the interface to the target filter, if existing, anyway.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (FELIX-385) ReferenceMetadata.setTarget includes the interface name in the target filter

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

Felix Meschberger closed FELIX-385.
-----------------------------------


Uploaded SNAPSHOT build number 20071001.145653-5 containing the fix.

Now closing this issue.

> ReferenceMetadata.setTarget includes the interface name in the target filter
> ----------------------------------------------------------------------------
>
>                 Key: FELIX-385
>                 URL: https://issues.apache.org/jira/browse/FELIX-385
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: 1.0.0
>
>
> When the target filter is set on a reference metadata, the interface name is included as a filter term. This is not required as the service access primarily uses the interface directly and service listener registration adds the interface to the target filter, if existing, anyway.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (FELIX-385) ReferenceMetadata.setTarget includes the interface name in the target filter

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

Felix Meschberger updated FELIX-385:
------------------------------------

    Fix Version/s:     (was: felix-1.0.0)
                   scr-1.0.0

> ReferenceMetadata.setTarget includes the interface name in the target filter
> ----------------------------------------------------------------------------
>
>                 Key: FELIX-385
>                 URL: https://issues.apache.org/jira/browse/FELIX-385
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR)
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: scr-1.0.0
>
>
> When the target filter is set on a reference metadata, the interface name is included as a filter term. This is not required as the service access primarily uses the interface directly and service listener registration adds the interface to the target filter, if existing, anyway.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (FELIX-385) ReferenceMetadata.setTarget includes the interface name in the target filter

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

Felix Meschberger resolved FELIX-385.
-------------------------------------

    Resolution: Fixed

Not including the reference interface name anymore in the target filter.

Fixed in Rev. 580901.

> ReferenceMetadata.setTarget includes the interface name in the target filter
> ----------------------------------------------------------------------------
>
>                 Key: FELIX-385
>                 URL: https://issues.apache.org/jira/browse/FELIX-385
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: 1.0.0
>
>
> When the target filter is set on a reference metadata, the interface name is included as a filter term. This is not required as the service access primarily uses the interface directly and service listener registration adds the interface to the target filter, if existing, anyway.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.