> Here is an alternate idea, something that would co-exist with the .sar > concept. Each MBean has a name that makes it unique. Build an XML file > with a name space, essentially an element for each MBean that has had its > configuration changed from the original .sar archive's jboss-service.xml > file. It is basically <cringe> a Windows Registry. If an MBean's > configuration is modified via, say the port 8082 HTML interface, an entry > is created if there wasn't one.
I think this is something which David was hinting at with his ref to jboss- auto.jcml... which is fine as long as it can be turned off. I personally to explicitly set the configuration which is used. I don't want to deal with some other registry and such. When I shutdown the VM I expect it to come back up with the original config. If I want that config changed then I will change the file. Others might like the configure once, then tune via GUI interface. Either should work... but lets not force everyone to a GUI. > configured. There could even be a "Revert to Defaults" button to switch > back to the original values in the .sar. So a GUI... blah > Another simpler idea, is to write a tool that opens a .sar, lets you > examine the MBean attributes, change them, and re-bundle them. No more > pains in the ass, and not very difficult. Hrm... did you even read the mail that I sent, or are you simply reacting to the subject? This sucks... I don't want to have to bring up some lame GUI to change a config value. > Maybe if the .sar JSR gets modified, maybe we will end up with .jar(s), > .war(s), and .ear(s) specifying if a *-service.xml file exists in the root > directory or the WEB-INF directory, a deployment manager will process > it. But for the time being, .sar deployment is a useful component. What .sar JSR ? --jason ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
