On Thu, 2002-07-25 at 09:27, Stephen McConnell wrote: > > > Jason van Zyl wrote: > > >On Wed, 2002-07-24 at 20:18, Stephen McConnell wrote: > > > > > >>Could anyone provide some thoughts about the configuration approach for > >>Sevak - as things stand at the moment the implementation is basically > >>setting up an embeded tomcat service, a host, connector, etc as part of > >>the initialize method. It would seem to make more sense to suck in a > >>configuration basically equivalent to the <service/> element in the > >>Tomcat server.xml file and build up the hosts, connectors, ... from there. > >> > >>Am I on the right track here ? > >> > >> > > > >You could ask the tomcat crew to make easily available their > >configuration mechanism so you can use the same tool (Digester) to parse > >the catalina configuration files. For turbine this would be useful: > >people could easily flip from using servlet container stand-alone to > >using an avalon container as _the_ container. > > > > Actually I was thinking about dragging this in via an Avalon > configuration instance.
For something as complicated as Catalina does that really make sense? There will undoubtedly be mismatches and if the configuration options change in Catalina then you are forced to update your configuration mechanism. I realize in a lot of cases that the Avalon configuration mechanism makes sense but in this case I think you would simplify things by using what's there. > That will enable management of default > configurations What about a default Catalina configuration file? > and generally a massive simplification of the deployment > process for the end-user What if the end user is accustomed to configuring Catalina in the standard fashion? Catalina is also JMX and it provides an interface for setting up contexts and connection/protocol handlers and all that jazz. (via cascading configs and packaged profiles). Sorry, not up on cascading configs and packaged profiles but I assume you are talking about running multiple instances of the embedded server with slightly different options in the configuration, yes? If so, I don't really see this being a highly utilized use case as opposed deploying multiple webapps inside a single Catalina instance. If not, then please explain further. Or possibly allow both. I know that I'm looking for a way for users to move easily from using Catalina stand-alone to using Catalina within an Avalon container and I'm not going to make users learn another configuration or management mechanism. > Steve. > > -- > > Stephen J. McConnell > > OSM SARL > digital products for a global economy > mailto:[EMAIL PROTECTED] > http://www.osm.net > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
