Tomcat backward compatbility loss VirtualHost->Alias mapping ------------------------------------------------------------
Key: JBAS-1301 URL: http://jira.jboss.com/jira/browse/JBAS-1301 Project: JBoss Application Server Type: Bug Components: Web (Tomcat) service Versions: JBossAS-4.0.1 Final, JBossAS-3.2.6 Final Reporter: Andrew Oliver Assigned to: Scott M Stark Priority: Minor In JBoss 3.2.3 (Tomcat 4.x) it was possible to create a Virtual Host and set of Aliases in the jboss-service.xml and then map the webapps to the aliases through the app deployment descriptors. In tomcat 5 this works for *some* apps that have been deployed. The rest throw a 400 error saying no virtual host has been configured. The same apps mapped directly to the actual vhost (not alias) do not throw this error. The previous behavior can be useful for builds which target multiple environments (stage/test/prod/etc). Moreover it should be preserverd for backward compatibility. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development