[
https://issues.jboss.org/browse/AS7-4543?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler commented on AS7-4543:
-------------------------------------
Done
{code}
[standalone@localhost:9999 /] deploy --name=foo
~/jboss-osgi-1.2.0-SNAPSHOT/bundles/org.apache.felix.eventadmin.jar
[standalone@localhost:9999 /] /subsystem=osgi/bundle=foo:start
{"outcome" => "success"}
[standalone@localhost:9999 /]
{code}
Allow bundle start/stop operations to work with deploy name
-----------------------------------------------------------
Key: AS7-4543
URL:
https://issues.jboss.org/browse/AS7-4543
Project: Application Server 7
Issue Type: Task
Components: OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.1.2.Final-redhat1
Currently it would be really awkward to install/start a bundle from the cli.
* deploy foo
* find the bundle id (subsystem=osgi:read-resource(recursive=true,include-runtime=true))
* subsystem=osgi:start(id=xx)
Instead this should be done like
* deploy foo
* start foo
--
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