[ https://issues.jboss.org/browse/AS7-931?page=com.atlassian.jira.plugin.sy... ] David Bosschaert updated AS7-931: --------------------------------- Summary: Expose OSGi subsystem configuration through management API (was: Expose OSGi configuration through management API) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-931?page=com.atlassian.jira.plugin.sy... ] Thomas Diesler reopened AS7-931: -------------------------------- Could you please add some coverage to the wiki on the set of supported operations/attibutes that manage the osgi subsystem? There is an important distinction between the OSGi subsystem already being activated or not. Some of the configuration affect boot time only (i.e. activation, modules). How do changes of these properties affect the subsystem? Generally, should boot time config even be writeable? How is adding/removing a module that effects system classpath packages supposed to work? I believe that framework properties are read-only by spec. Is this reflected in the management operations? I realize and assume that much of the existing code is part of a learning exercise. Following this I suggest to go back to the drawing board and define a concise set of mgmnt operations that make sense for the OSGi subsytem. A discussion on the ml (referenced from here) would also be cool. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira