David Jencks wrote: > I have an alternate proposal that I think might work. Let's make it > really easy to construct host gbeans in a tomcat plan or tomcat config > in a generic web plan. These host gbeans will go in the app that > defines them. This will put the problems squarely in the users lap, but > help them solve them easily. > > So, we could have something like a choice of host-ref that takes a name > and looks for an existing host, and host that takes a name and has > multiple alias subelements: this would create a new host with the given > name and aliases. > > How many unanticipated problems would this cause :-) ? Are there other > properties of the host we need to be able to set easily?
The list of Host attributes are found here: http://tomcat.apache.org/tomcat-5.5-doc/config/host.html I am not sure that setting a host configuration in the web app is appropriate as you then may have clashes when other web apps need to use the host. > > thanks > david jencks > >> >> Thanks, >> Aaron
