[
https://issues.jboss.org/browse/AS7-2041?page=com.atlassian.jira.plugin.s...
]
David Bosschaert commented on AS7-2041:
---------------------------------------
Just as a sanity check, when this is fixed the following should work.
First, activate the OSGi subsystem:
{code}] cd /subsystem=osgi
subsystem=osgi] :write-attribute(name=activation,value=eager)
{code}
The OSGi subsystem will now activate. Then the following should return proper values:
{code}subsystem=osgi] :read-children-resources(child-type=bundle,include-runtime=true)
{
"outcome" => "success",
"result" => {
"0" => ... should be some value...,
"1" => ... should be some value too...,
{code}
Note that reading an individual bundle resource works fine at the moment:
{code} subsystem=osgi] cd bundle=1
bundle=1] :read-resource(include-runtime=true)
{
"outcome" => "success",
"result" => {
"id" => 1L,
"startlevel" => 1,
"state" => "INSTALLED",
"symbolic-name" => "javaee.api",
"version" => "0.0.0"
}
}
{code}
read-children-resources with include-runtime is broken
------------------------------------------------------
Key: AS7-2041
URL:
https://issues.jboss.org/browse/AS7-2041
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.0.Alpha1
Reporter: David Bosschaert
When adding the include-runtime attribute to :read-children-resources the result is
always undefined.
When, in the CLI I do:
{code}
subsystem=osgi] :read-children-resources(child-type=capability,include-runtime=true)
{
"outcome" => "success",
"result" => {
"javaee.api" => undefined,
"org.apache.aries.jmx" => undefined,
"org.apache.aries.util" => undefined,
"org.apache.felix.configadmin" => undefined,
"org.apache.felix.eventadmin" => undefined,
"org.apache.felix.log" => undefined,
...
{code}
In the above example, if I remove 'include-runtime' things do work normally.
I need include-runtime to properly work for the GUI side of subsystem=osgi/bundle=* since
all of the attributes of that resources are runtime only ones.
--
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