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] Commented: (FELIX-2584) No FrameworkEvent.ERROR on unchecked exception in event listener
Date Tue, 28 Sep 2010 15:33:33 GMT

    [ https://issues.apache.org/jira/browse/FELIX-2584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915788#action_12915788

Richard S. Hall commented on FELIX-2584:

Not sure what you mean by "FrameworkEvents should be mapped by a logging service"... If there
is no logging service or no framework listeners, then failures would go unlogged. It seems
reasonable to log them. The framework has no way of knowing if there is someone out there
listening to events and relaying the ERROR events to anyone, so it doesn't make sense just
to swallow them.

> No FrameworkEvent.ERROR on unchecked exception in event listener
> ----------------------------------------------------------------
>                 Key: FELIX-2584
>                 URL: https://issues.apache.org/jira/browse/FELIX-2584
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework, Specification compliance
>    Affects Versions: framework-3.0.2
>            Reporter: Eduardo Tsen
>            Assignee: Richard S. Hall
>             Fix For: framework-3.2.0
> The OSGi-Spec states on page 116:
> "The Framework must publish a FrameworkEvent.ERROR if a callback to an event listener
generates an unchecked exception - except when the callback happens while delivering a FrameworkEvent.ERROR
(to prevent an infinite loop)."
> The EventDispatcher, in contrast, just logs those exceptions with no further action taken.

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

View raw message