Hi Guillaume,
it's sufficient, but I got comments from users saying:
- it's not easy to understand and use
- it's far from the Karaf config:* commands
- when I change a configuration, the changes are not "flushed" to the
etc cfg file (whereas the config:* commands do)
That's why I proposed to create some kind of wrapper MBeans specific for
Karaf.
Regards
JB
On 09/22/2011 09:54 PM, Guillaume Nodet wrote:
Wasn't the COnfigurationAdminMBean interface defined by the osgi spec
sufficient ?
On Thu, Sep 22, 2011 at 19:03, Jean-Baptiste Onofré<[email protected]> wrote:
It's done Johan.
You have the ConfigMBean now supporting the following operations:
list()
create(pid)
delete(pid)
proplist(pid)
propdelete(pid, key, bypassStorage)
propappend(pid, key, value, bypassStorage)
propset(pid, key, value, bypassStorage)
I'm working on the others MBeans, it should be ready for tomorrow evening
(my time).
Regards
JB
On 09/22/2011 06:59 PM, Johan Edstrom wrote:
Dunno if it is on the list but doing things like
listing pid's for config and adding / reading / modifying factories would
be nice.
I think the listing pids is missing in 2.2.2 at least. Or in Aries
actually.
On Sep 22, 2011, at 10:53 AM, Jean-Baptiste Onofré wrote:
Agree Mike.
I'm working on new MBeans for Karaf 2.2.4. I know that it's expected by a
significant number of users.
Regards
JB
On 09/22/2011 06:29 PM, mikevan wrote:
I like that idea. We're having to do that now in our instance of Karaf,
and
its a bit painful. it would be nice for Karaf to automatically create
mbeans for each bundle deployed, something akin to what Camel does with
routes.
Jean-Baptiste Onofré wrote:
Hi Guillaume
Yes, it is but you can make the equivalent of osgi:install mvn:....
That the purpose: add some actions Karaf related.
Regards
JB
On 09/07/2011 06:56 PM, Guillaume Nodet wrote:
Bundles and config are already available via the standardized osgi
mbeans provided by aries afaik.
Did I miss something ?
On Wed, Sep 7, 2011 at 15:49, Jean-Baptiste Onofré<[email protected]
>
wrote:
Hi all,
I'm working on KARAF-786 in order to add a bunch of new MBeans in
Karaf.
The purpose is to be able to manipulate bundles, config, security,
scheduler, kar, via the JMX.
Currently the management Maven module is the bootstrap to start the
Karaf
MBean server.
I would like to make the following refactoring:
- management will be a POM containing two Maven modules: server and
mbeans
- the server module is the current management, aka the MBean server
bootstrap
- the mbeans is a POM that will contains one Maven module per MBean
type:
bundle, config, etc (it looks like that we have in the shell Maven
module).
Are you OK with that ?
Regards
JB
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
-----
Mike Van
Mike Van's Open Source Technologies Blog
--
View this message in context: http://karaf.922171.n3.nabble.**
com/PORPOSAL-Little-**refactoring-of-the-Karaf-**
management-tp3316724p3359338.**html<http://karaf.922171.n3.nabble.com/PORPOSAL-Little-refactoring-of-the-Karaf-management-tp3316724p3359338.html>
Sent from the Karaf - Dev mailing list archive at Nabble.com.
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
