DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=32865>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=32865 ------- Additional Comments From [EMAIL PROTECTED] 2004-12-28 22:59 ------- I urge you to reconsider: 1) the flag is not removed, there is still a property deployOnStartup, settable in server.xml (sure in this case it may be useless) or settable on the MBean (in which case it is very useful, for fine grained control of which apps get deployed, and to configure the Contexts through JMX prior to deployment). It is also documented, and worked in 5.0.x, 4.x.x and prior. 2) the patch causes no harm, if someone does not set deployOnStartup, it is true by default. The patch just restores the previous documented functionality. 3) is there any reason for removing the flag, and why do you feel it is useless? I am trying to embed Tomcat using JMX, and the ignoring of the deployOnStartup flag is causing all kinds of problems. I need to set useNaming to false on the contexts, and since DefaultContext is gone, the only way I can see to do this is on the context themselves. I want to do this programmatically (through JMX), not trhough yet another xml file. Regards Tony BenBrahim -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
