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] Updated: (FELIX-1237) STOPPING & STOPPED events not fired when activator throws exception
Date Mon, 15 Jun 2009 16:26:07 GMT

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

Richard S. Hall updated FELIX-1237:
-----------------------------------

    Component/s: Specification compliance

> STOPPING & STOPPED events not fired when activator throws exception
> -------------------------------------------------------------------
>
>                 Key: FELIX-1237
>                 URL: https://issues.apache.org/jira/browse/FELIX-1237
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework, Specification compliance
>    Affects Versions: felix-1.8.0
>         Environment: generic
>            Reporter: Sahoo
>            Assignee: Richard S. Hall
>             Fix For: felix-1.8.1
>
>
> As per the spec,
> If the start(BundleContext) method throws an exception, the Framework must mark the bundle
as stopped and send out STOPPING and STOPPED events but it must not call the Bundle Activator
stop(BundleContext) method.
> Looking at the implementation in  "void startBundle(BundleImpl bundle, boolean record)"
 in Felix.java, I don't see framework firing any events when activator throws an exception.

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


Mime
View raw message