I won't pretend I have fully got my head around this yet. :) To summarise my understanding so far: JBM 2.0 will have a simple POJO based management API. What we would like to do is: 1) Expose that API as a web interface (I'm guessing this is what Charles demo'd at JBW) 2) Also expose that API as a non web interface (is this Swing?) which can be controlled from a remote client. The management stuff needs to know what attributes and operations we want to expose - I'm assuming that's the purpose of the plugin. Given a plugin, I'm assuming the management layer is smart enough to be able to provide a web or non web (remote) interface. (This is just a view on the same underlying API). We want to avoid non standard JDK annotations in our POJOs to define management interfaces, since JBM is also designed to be included in Joe Bloggs third party project and we don't want to force them to pull in an unnecessary build time dependency on other (MC) jboss libraries. If all this is to run in the MC, I am also interested in what runtime dependencies are needed for this all to function. So far I have gleaned: 1) JBossWeb 2) Seam 3) Remoting 2 4) Profile service (?) Anything else? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130641#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...