marc fleury wrote: > Sacha, > > this is configuration for JBoss4.0. > > The fact is that for *production* the one file is good. > > For actually administering and configuring a server the many files is > better, yes, but they are different world, the notion of "locking down" a > server is VERY REAL.
Sure. I do that by setting permissions of the config and deploy directories such that only the JBoss user can do anything (including read). What good does having one big honking file do here? I agree that it does no harm, but I don't see how it 'locks down' the server. > In the admin/configuration category, the persistence > of the configuration above and beyond the current xml is not done right now > the fact that it is mixed with the creation is a weakness we are carrying > over from the 2.0 days. > Right, to really fix that will have to be a 4.0 issue. Once that works, JBoss will be administrable from whatever can use JMX - JSR 88 based tools, SNMP management tools, etc. my .02$ danch _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
