[ http://issues.apache.org/jira/browse/GERONIMO-1460?page=comments#action_12362587 ]
David Jencks commented on GERONIMO-1460: ---------------------------------------- After discussing this with Jeff Genender, we don't think this is possible to implement in a meaningful way. I don't think the description is clear: I believe the intent to be to support directly specifying multiple virtual hosts for tomcat as they are currently specified for jetty (see GERONIMO-1461) The constraints in the tomcat architecture are: 1. each web app context has to be associated to exactly one host object 2. each host object contains one (zero?) or more "alias" strings which correspond to the jetty "virtual host" strings. 3. No two host objects can contain the same alias string. It's easy to see that most of the time when you associate a set of aliases with more than one web app context there is no way to construct hosts that supply those aliases to the web app contexts. For instance, if web app A has aliases v1 and v2, and web app B has aliases v2 and v3, we would need hosts H1 containing v1 and v2 and H2 containing v2 and v3, violating rule (3). Due to these contraints, we usually cannot automatically resolve the best way to supply a set of hosts that break the users expectations the least, and we should leave it up to the users to resolve this by hand according to their needs. If no one presents a counter argument I will close this as invalid. > Tomcat web plan should take multiple hosts, create HostGBeans as necessary > -------------------------------------------------------------------------- > > Key: GERONIMO-1460 > URL: http://issues.apache.org/jira/browse/GERONIMO-1460 > Project: Geronimo > Type: Improvement > Components: Tomcat, web > Versions: 1.0 > Reporter: Aaron Mulder > Assignee: Jeff Genender > Fix For: 1.1 > > The Tomcat web plan should take multiple <host> elements, and for each one: > - if a HostGBean is present, associate to that > - if a HostGBean is not present, create a default one and start it, and then > associate to that -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
