[
https://jira.jboss.org/jira/browse/JBOSGI-112?page=com.atlassian.jira.plu...
]
Thomas Diesler resolved JBOSGI-112.
-----------------------------------
Fix Version/s: JBossOSGi 1.0.0 Beta3
(was: JBossOSGi 1.0.x)
Resolution: Done
BJ Hargrave sais:
Exceptions thrown from listeners are logged but otherwise ignored. So throwing an
exception from a listener will not prevent the bundle from proceeding with starting.
If the BP extender detects some issue with the BP configuration, it can/should log this
information but it cannot prevent the bundle from starting.
Investigate Exception in SynchronousBundleListener
--------------------------------------------------
Key: JBOSGI-112
URL:
https://jira.jboss.org/jira/browse/JBOSGI-112
Project: JBoss OSGi
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.0 Beta3
http://www.osgi.org/javadoc/r4v41/org/osgi/framework/SynchronousBundleLis...
"Unlike normal BundleListener objects, SynchronousBundleListeners are synchronously
called during bundle lifecycle processing. The bundle lifecycle processing will not
proceed until all SynchronousBundleListeners have completed. SynchronousBundleListener
objects will be called prior to BundleListener objects. "
IMHO, an extender that registers a SynchronousBundleListener should be able to cause the
Bundle.start() operation to fail.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira