felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard S. Hall (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (FELIX-2555) Log messages should contain the bundle id, when available
Date Wed, 15 Sep 2010 20:53:32 GMT

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

Richard S. Hall resolved FELIX-2555.

      Assignee: Richard S. Hall
    Resolution: Fixed

Committed patch. Please close this big if you are satisfied. Thanks!

> Log messages should contain the bundle id, when available
> ---------------------------------------------------------
>                 Key: FELIX-2555
>                 URL: https://issues.apache.org/jira/browse/FELIX-2555
>             Project: Felix
>          Issue Type: Improvement
>          Components: Framework
>    Affects Versions: framework-3.0.1
>            Reporter: Don Brown
>            Assignee: Richard S. Hall
>             Fix For: framework-3.0.3
>         Attachments: FELIX-2555.diff
> Felix currently provides some great information about a class loading failure in the
debug log, and nothing other than the name for resource failures.  However, this means the
first step in diagnosing any problem is to have the user restart the app with the debug level
turned down to debug, then try to reproduce the problem.
> While I agree with the comments in FELIX-1022 that the level of work to create the class
not found diagnostic message is too much for normal operation, I believe Felix should at least
log the related bundle whenever it can.  This allows the embedding application to collect
logs for a bundle and optionally log additional information to help diagnostics.
> Logger currently has methods for logging messages against a particular ServiceReference,
and there should similarly be a log() method that takes the Bundle, or at least, the bundle
id.  This would allow Felix to log class and resource not founds, for example, with the bundle
id, greatly improving debugging.

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

View raw message