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] [Resolved] (FELIX-4673) Log any error thrown when trying to create a null object.
Date Thu, 16 Oct 2014 13:40:34 GMT

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

Pierre De Rop resolved FELIX-4673.
----------------------------------
    Resolution: Fixed

ok, I just commited a patch in rv 1632304:

- any exceptions thrown when creating a null object are now logged using the log service.
- same for exceptions thrown when invoking any "propagate callback instances" or when trying
to instantiate a default component implementation.
- Also, fixed DM Logger, which was not tracking log service.


> Log any error thrown when trying to create a null object.
> ---------------------------------------------------------
>
>                 Key: FELIX-4673
>                 URL: https://issues.apache.org/jira/browse/FELIX-4673
>             Project: Felix
>          Issue Type: Improvement
>          Components: Dependency Manager
>    Affects Versions: dependencymanager-3.2.0
>            Reporter: Marcel Offermans
>            Assignee: Pierre De Rop
>             Fix For: dependencymanager-4.0.0
>
>
> Currently, the dependency manager will log an error if an exception occurs while trying
to create a null object. However, it can also encounter a NoClassDefFoundError (when a bundle
is misconfigured for some reason). Such errors should probably also be caught and logged.
> See getNullObject() in ServiceDependencyImpl.



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

Mime
View raw message