[
https://issues.jboss.org/browse/AS7-4840?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler commented on AS7-4840:
-------------------------------------
Yes, this CLI/Console is the same thing. Operation 'deploy' does a 'bundle
install' - there is no implicit 'bundle start'
The reason is that we don't want to create an implicit ordering requirement on the
'deploy' operation. IOW it should be possible to deploy artefacts in any order. I
suspect that future AS7 versions will have a --start flag on the deploy operation.
OSGi subsystem does not call BundleActivator
--------------------------------------------
Key: AS7-4840
URL:
https://issues.jboss.org/browse/AS7-4840
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.1.2.Final (EAP)
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