felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] Closed: (FELIX-2372) Improve logging on IllegalStateException getting a service
Date Mon, 16 Aug 2010 12:12:26 GMT

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

Felix Meschberger closed FELIX-2372.

Apache Felix Declarative Services 1.6.0 has been released. The issues are now closed.

> Improve logging on IllegalStateException getting a service
> ----------------------------------------------------------
>                 Key: FELIX-2372
>                 URL: https://issues.apache.org/jira/browse/FELIX-2372
>             Project: Felix
>          Issue Type: Improvement
>          Components: Declarative Services (SCR)
>    Affects Versions:  scr-1.4.0
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For:  scr-1.6.0
> BundleContext.getService() may throw an IllegalStateException if the bundle context is
invalid. In addition the Felix implementation may also throw this exception of the service
to be trieved is a ServiceFactory whose real service cannot be retrieved due to a cycle in
service dependencies.
> The DependencyManager should log this exception clearly to help solve the actual problem.
> In the current Felix Declarative Service implementation such a loop can be created if
there is a depedency loop amongst delayed service components, like this:
>     Delayed Component A, provides Service A, requires Service C
>     Delayed Component B, provides Service B, requires Service A
>     Delayed Component C, provides Service C, requires Service B
> Such cycles should actually be detected by SCR (Declarative Services Specification Section
112.3.5, Circular References), but this is not currently implemented, see FELIX-1824. Still,
such cycles may of course exist amongst services registered outside of the Declarative Services
world, in which case, such an exception may still occur.

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

View raw message