felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Phillips (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FELIX-4802) Aggregate Dependency with Field Injection does not respect SERVICE_RANKING
Date Fri, 20 Feb 2015 15:15:12 GMT

     [ https://issues.apache.org/jira/browse/FELIX-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andy Phillips updated FELIX-4802:
---------------------------------
    Description: 
I found an issue with the Aggregate Dependency with Field Injection where i have a list of
"services" that i would like to maintain with a manager.   The order of the services is important.


I noticed that the field injection, say:
@Component
public class HelloConsumer {
     @Requires
     private Hello m_hellos[]; // Array => Aggregate
     public doSomething() {
             for(int I = 0; I < m_hellos.length; i++) { 
                 System.out.println(m_hellos[i].getMessage());
             }
       }
}

The initial list when the instance is "created" appears to respect the SERVICE_RANKING, but
subequent modifications (say you install a new bundle with an additional "hello") does not
respect the SERVICE_RANKING in the order.   I will have to end up do my own sorting on the
list prior to using the field.  

Is this normal?  I feel that the SERVICE_RANKING should always be respected on the list of
m_hellos[]s....

  was:
I found an issue with the Aggregate Dependency with Field Injection where i have a list of
"services" that i would like to maintain with a manager.   The order of the services is important.


I noticed that the field injection, say:
@Component
public class HelloConsumer {
     @Requires
     private Hello m_hellos[]; // Array => Aggregate
     public doSomething() {
             for(int I = 0; I < m_hellos.length; i++) { 
                 System.out.println(m_hellos[i].getMessage());
             }
       }
}

The initial list when the instance is "created" appears to respect the SERVICE_RANKING, but
subequent modifications (say you install a new bundle with an additional "hello") does not
respect the SERVICE_RANKING in the order.   I will have to end up do my own sorting on the
list prior to using the field.  

Is this normally.


> Aggregate Dependency with Field Injection does not respect SERVICE_RANKING
> --------------------------------------------------------------------------
>
>                 Key: FELIX-4802
>                 URL: https://issues.apache.org/jira/browse/FELIX-4802
>             Project: Felix
>          Issue Type: Bug
>          Components: iPOJO
>    Affects Versions: ipojo-runtime-1.12.1
>         Environment: I found this using Apache Karaf 3.0.3
>            Reporter: Andy Phillips
>
> I found an issue with the Aggregate Dependency with Field Injection where i have a list
of "services" that i would like to maintain with a manager.   The order of the services is
important. 
> I noticed that the field injection, say:
> @Component
> public class HelloConsumer {
>      @Requires
>      private Hello m_hellos[]; // Array => Aggregate
>      public doSomething() {
>              for(int I = 0; I < m_hellos.length; i++) { 
>                  System.out.println(m_hellos[i].getMessage());
>              }
>        }
> }
> The initial list when the instance is "created" appears to respect the SERVICE_RANKING,
but subequent modifications (say you install a new bundle with an additional "hello") does
not respect the SERVICE_RANKING in the order.   I will have to end up do my own sorting on
the list prior to using the field.  
> Is this normal?  I feel that the SERVICE_RANKING should always be respected on the list
of m_hellos[]s....



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message