[
https://jira.jboss.org/jira/browse/JBOSGI-181?page=com.atlassian.jira.plu...
]
Thomas Diesler resolved JBOSGI-181.
-----------------------------------
Resolution: Done
The scan listener issue is fixed. We also now provide EventAdmin service support
Running org.jboss.test.osgi.example.event.EventAdminTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.296 sec
Add EventAdmin as available service
-----------------------------------
Key: JBOSGI-181
URL:
https://jira.jboss.org/jira/browse/JBOSGI-181
Project: JBoss OSGi
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Compendium Services
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 1.0.0 Beta5
Currently the DeploymentScannerService provides its own ScanListener the OSGiBootstrap
hooks into in order to report how long the first scan and provisioning of the initial
bundles took.
This creates a dependency on deployment API at the SPI level.
EventAdmin should be used for general inter bundle communication.
--
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