hi,
> 5- gui? pfffff it would need to be a JMX gui in our case, why not, but
> everybody talks about these and no-one does jack.
i think what Dr. Jung mentioned @ JBossOne would be a killer: expose the
MBeans via SOAP and construct a Microsoft Management Console Plugin to
configure/maintain JBoss from that beast.
other than that, my 2 (albeit euro) cents on the subject of the config
files:
i don't give one cent on how the config file looks like (i.e. XML,
key=value, ...) AS LONG AS I CAN EDIT IT WITH MY TEXT-EDITOR OF CHOICE.
consolidation/deconsolidation of the configuration has its own pros and
cons. personally i would like to have both available: small files for
development/testing purposes (un-deploy of an MBean by simply issuing
'mv mbean.jar ../nodepoy') and one huge file for locking down my
production servers.
i *think* you can achieve both by using several XML files which can be
merged (at the users option, with a *simple* command) into one big XML
file: develop/test with the small ones until you're happy. hit the
"lockdown config" button. get a large file which is the sum of the small
ones. xml namespaces might come in handy here?!
rgds,
christian
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
