2:16 a.m.
Thomas Diesler created AS7-4543:
-----------------------------------
Summary: 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
4:04 a.m.
[
https://issues.jboss.org/browse/AS7-4543?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler commented on AS7-4543:
-------------------------------------
An example sequence is
{code}
[standalone@localhost:9999 /] deploy --name=org.apache.felix.eventadmin
~/jboss-osgi-1.2.0-SNAPSHOT/bundles/org.apache.felix.eventadmin.jar
[standalone@localhost:9999 /]
/subsystem=osgi:read-children-resources(child-type=bundle,recursive=true,include-runtime=true)
{
"outcome" => "success",
"result" => {
"0" => {
"id" => 0L,
"startlevel" => 0,
"state" => "ACTIVE",
"symbolic-name" => "system.bundle",
"type" => "bundle",
"version" => "0.0.0"
},
"1" => {
"id" => 1L,
"startlevel" => 1,
"state" => "RESOLVED",
"symbolic-name" => "osgi.enterprise",
"type" => "bundle",
"version" => "4.2.0.201003190513"
},
"2" => {
"id" => 2L,
"startlevel" => 1,
"state" => "RESOLVED",
"symbolic-name" => "javax.servlet.api",
"type" => "bundle",
"version" => "2.5.0.Final"
},
"3" => {
"id" => 3L,
"startlevel" => 1,
"state" => "ACTIVE",
"symbolic-name" => "org.apache.felix.log",
"type" => "bundle",
"version" => "1.0.0"
},
"4" => {
"id" => 4L,
"startlevel" => 1,
"state" => "ACTIVE",
"symbolic-name" => "jboss-osgi-logging",
"type" => "bundle",
"version" => "1.0.0"
},
"5" => {
"id" => 5L,
"startlevel" => 1,
"state" => "ACTIVE",
"symbolic-name" => "org.apache.felix.configadmin",
"type" => "bundle",
"version" => "1.2.8"
},
"6" => {
"id" => 6L,
"startlevel" => 1,
"state" => "ACTIVE",
"symbolic-name" => "jboss-as-osgi-configadmin",
"type" => "bundle",
"version" => "7.1.2.Final-SNAPSHOT"
},
"7" => {
"id" => 7L,
"startlevel" => 1,
"state" => "INSTALLED",
"symbolic-name" => "org.apache.felix.eventadmin",
"type" => "bundle",
"version" => "1.2.6"
}
}
}
[standalone@localhost:9999 /] /subsystem=osgi/bundle=7: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
8:14 a.m.
[
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
8:14 a.m.
[
https://issues.jboss.org/browse/AS7-4543?page=com.atlassian.jira.plugin.s...
]
Thomas Diesler edited comment on AS7-4543 at 4/18/12 9:13 AM:
--------------------------------------------------------------
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"}
{code}
was (Author: thomas.diesler):
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
5125
days inactive
5125
days old
3 comments
1 participants
participants (1)
-
Thomas Diesler (JIRA)