> 8. Tomcat should work with no config file - using only JMX > API calls to load it and configure a set of plugins ( profile > ), using whatever class loader and layout the embeding > application ( ant, etc ) wants.
I've toyed with a thought along that line before. My train of thought was roughly, say you start Tomcat with a command line option for port or whatever. Then configure it using say JMX, then being able to save the "modelled" configuration out to a file that can be used in subsequent startups, or being possible to roll out on deployments or whatever. Or is that already possible (sorry I'm not up to speed with the admin app, I know it can create the server.xml, but were talking another level of config here right?) Martin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
