felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre De Rop (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FELIX-4910) ComponentExecutorFactory does not allow to return null from getExecutorFor method.
Date Fri, 05 Jun 2015 20:01:00 GMT

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

Pierre De Rop updated FELIX-4910:
---------------------------------
    Fix Version/s:     (was: org.apache.felix.dependencymanager-r4)
                    	org.apache.felix.dependencymanager-r5

> ComponentExecutorFactory does not allow to return null from getExecutorFor method.
> ----------------------------------------------------------------------------------
>
>                 Key: FELIX-4910
>                 URL: https://issues.apache.org/jira/browse/FELIX-4910
>             Project: Felix
>          Issue Type: Bug
>          Components: Dependency Manager
>    Affects Versions: org.apache.felix.dependencymanager-r3
>            Reporter: Pierre De Rop
>            Assignee: Pierre De Rop
>             Fix For:  	org.apache.felix.dependencymanager-r5
>
>
> When providing a ComponentExecutorFactory in the OSGi service registry, then all components
that are not black listed by the "org.apache.felix.dependencymanager.parallel" system property
are managed and started concurrently, using the executor returned by the ComponentExecutorFactory.getExecutorFor(Component
c) method.
> This issue concerns the case when the getExecutorFor(Component c) method returns null,
which normally indicates that the component should be handled synchronously (like in the normal
case), and not concurrently.
> But currently, returning null from getExecutorFor() method is not supported and does
not work.



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

Mime
View raw message