What is the ultimate purpose of this? AFAICS this would add a module to
the osgi subsystem description, which could on subsystem startup provide
packages that are available on the osgi system classloader. These
packages would however only be visible if corresponding export
statements are defined too.
From an osgi subsystem management perspective, I'd think it is more
useful to provide management functionality like start/stop of a bundle.
Another obvious candidate would be the management of ConfigAdmin properties.
cheers
-thomas
On 05/31/2011 02:22 PM, David Bosschaert wrote:
Hi all,
I'm currently learning the AS7 management API so I can work on providing additional
management functionality.
As a start, I've extended the OSGi management API so that a pre-loaded module can be
added/removed.
Before I go add more stuff to this I would appreciate if someone could quickly review
what I did, just to make sure I didn't miss anything...
The changes are this branch:
https://github.com/bosschaert/jboss-as/commit/ba78cf975ba86a7cba9a195f001...
Thanks!
David
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx