[
https://issues.jboss.org/browse/JBOSGI-556?page=com.atlassian.jira.plugin...
]
Thomas Diesler resolved JBOSGI-556.
-----------------------------------
Resolution: Rejected
{code}
[standalone@localhost:9999 /] deploy --name=foo
~/Downloads/SimpleOSGi_1.0.0.201205181614.jar
[standalone@localhost:9999 /] /subsystem=osgi/bundle=foo:start
{"outcome" => "success"}
{code}
{code}
08:53:25,634 INFO [org.jboss.osgi.framework] (MSC service thread 1-3) JBOSGI011001:
Bundle installed: SimpleOSGi:1.0.0.201205181614
08:53:25,928 INFO [org.jboss.as.server] (management-handler-thread - 1) JBAS018559:
Deployed "foo"
08:53:51,118 INFO [stdout] (management-handler-thread - 4) OSGi bundle started
08:53:51,120 INFO [org.jboss.osgi.framework] (management-handler-thread - 4)
JBOSGI011002: Bundle started: SimpleOSGi:1.0.0.201205181614
{code}
OSGi subsystem does not call BundleActivator
--------------------------------------------
Key: JBOSGI-556
URL:
https://issues.jboss.org/browse/JBOSGI-556
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Core Framework
Affects Versions: JBossOSGi 1.3.0
Reporter: Rico Neubauer
Assignee: Thomas Diesler
Labels: osgi
Attachments: SimpleOSGi_1.0.0.201205181614.jar
Occurs with JBoss 7.1.2.Final (EAP) running with jbosgi-framework 1.3.0.Final
OSGi activators do not get called after bundle starts. Instead nothing happens.
Test bundle attached, but happens with any activator bundle.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira