This should not be a black and white option. We need a logical seperation from configuration from the deployment at the JBoss core layer. If someone wants to persist configuration with the deployment, including runtime mods let them.
If someone wants to access webdav, jdbc, jndi, etc. for the configuration, let them. Quit being purists and address the administration problem. This does need to be in 3.2. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Dain Sundstrom" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, January 13, 2003 11:59 AM Subject: Re: [JBoss-dev] MBean persistence? ... ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development