"mazz(a)jboss.com" wrote : Let me be clear, too - RHQ does NOT introduce ANY
dependencies in YOUR managed product. You have no RHQ code in jbm at all. I only bring up
JMX because that's the "standard" way to manage Java apps/services. You can
do it however you want.
I'm talking about the dependencies that RHQ requires to run. This all needs to run in
the JBM "server" (the MC)
Let me clarify.
User Joe Bloggs will download the JBM "standalone" config which is a super
lighweight MC installation running JBM POJOs. The idea is for that JBM instance to provide
a management interface. If we use RHQ to do that it needs to be running in that MC too, so
it's dependencies are very relevant.
The user is not going to be starting up any other RHQ serves just so they can see the JBM
interface, that would suck.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130812#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...