Friday, March 20, 2009

Working on a standalone PluginContainer wrapper

I have been working on a standalone plugin container wrapper for RHQ and Jopr which allows to call plugin functionality without the need for a fully running agent and server. Of course this only makes sense while developing a plugin.

This video shows how this may look like (swf format).

This stuff is not yet committed to subversion, but I guess I will do that in the next few days.

Please provide feeback.


Jay said...

This is a great idea. I'd also suggest (if it's not present already) a way of separating out the plugin descriptor validator. Sure, that'll get run when the standalone container is created, but it'd be nice to be able to run it at a much smaller level.

What are you plans for the communications with the server? Going to mock those out? It might be handy to write them out to a file for more debugging of what's getting sent to the server.

- Jay (

Heiko W. Rupp said...

yeah, this is a good idea with the validator. Perhaps just an option on the shell command line to trigger this.

This standalone wrapper does not talk to the server at all as it is really meant as a simple way to invoke the various facet methods.

Tracing the communication would perhaps be an option for the real agent - Mazz will be happy to add another configuration option for it :-)

John Mazz said...

Ask and you shall already receive.

It is already possible to trace agent-server communications!

Using some log4j categories and system properties, you can log the comm messages to a file.

I even make it easier for you by providing the "debug" prompt command ("help debug" for more info).

See this wiki page on how you trace the communications: