[
http://jira.jboss.com/jira/browse/JBAS-1301?page=comments#action_12314745 ]
Andrew Oliver commented on JBAS-1301:
-------------------------------------
Is see this:
$ find ./tomcat -name "*.java" -exec grep -Hi "virtual" '{}' ';'
./tomcat/src/main/org/jboss/web/tomcat/security/JBossSecurityMgrRealm.java:
* trying to change the virtual host to which a Request should be
./tomcat/src/main/org/jboss/web/tomcat/tc4/authenticator/SingleSignOn.java: *
virtual host (typically an implementation of <code>Host</code>).</li>
./tomcat/src/main/org/jboss/web/tomcat/tc4/ConfigHandler.java: // Setup
the mapping rules for Engine virtual hosts
./tomcat/src/main/org/jboss/web/tomcat/tc4/EmbeddedCatalina.java:/** A subclass
of Embedded that accepts Services and locating virtual
./tomcat/src/main/org/jboss/web/tomcat/tc4/EmbeddedCatalina.java: * and
directed to the specified context path on the virtual host
./tomcat/src/main/org/jboss/web/tomcat/tc4/TomcatDeployer.java: Iterator
hosts = metaData.getVirtualHosts();
./tomcat/src/main/org/jboss/web/tomcat/tc4/TomcatDeployer.java: Host
virtualHost = config.getCatalina().findHost(hostName);
./tomcat/src/main/org/jboss/web/tomcat/tc4/TomcatDeployer.java:
new ClusterManager(virtualHost,
./tomcat/src/main/org/jboss/web/tomcat/tc4/TomcatDeployer.java:
virtualHost.addChild(context);
./tomcat/src/main/org/jboss/web/tomcat/tc4/TomcatDeployer.java:
virtualHost.getName(), config.getServiceName(), server);
./tomcat/src/main/org/jboss/web/tomcat/tc5/sso/ClusteredSingleSignOn.java: *
virtual host (typically an implementation of <code>Host</code>).</li>
./tomcat/src/main/org/jboss/web/tomcat/tc5/StatusServlet.java: //
Display virtual machine statistics
./tomcat/src/main/org/jboss/web/tomcat/tc5/TomcatDeployer.java: Iterator
hostNames = metaData.getVirtualHosts();
./tomcat/src/main/org/jboss/web/tomcat/tc5/TomcatDeployer.java: Iterator
hostNames = metaData.getVirtualHosts();
However I also see this:
$ find ./tomcat -name "*.java" -exec grep -Hi "alias" '{}' ';'
./tomcat/src/main/org/jboss/web/tomcat/tc4/ConfigHandler.java:
mapper.addCallMethod("Server/Service/Engine/Host/Alias", "addAlias",0);
./tomcat/src/main/org/jboss/web/tomcat/tc4/EmbeddedCatalina.java: //
Search all Hosts for matching names and aliases
./tomcat/src/main/org/jboss/web/tomcat/tc4/EmbeddedCatalina.java:
// Check the aliases
./tomcat/src/main/org/jboss/web/tomcat/tc4/EmbeddedCatalina.java:
String[] aliases = tmpHost.findAliases();
./tomcat/src/main/org/jboss/web/tomcat/tc4/EmbeddedCatalina.java:
for(int a = 0; a < aliases.length; a ++)
./tomcat/src/main/org/jboss/web/tomcat/tc4/EmbeddedCatalina.java:
String alias = aliases[a];
./tomcat/src/main/org/jboss/web/tomcat/tc4/EmbeddedCatalina.java:
if( alias.equalsIgnoreCase(hostName) == true )
And then if you look at that you find this:
// Check the aliases
String[] aliases = tmpHost.findAliases();
for(int a = 0; a < aliases.length; a ++)
{
String alias = aliases[a];
if( alias.equalsIgnoreCase(hostName) == true )
{
host = tmpHost;
break;
}
}
There is nothing similar in the TC5 jboss coupling code.
A quick glance though the TC5 code shows things that MAY have taken its place
but I'd have to run through it in a linear problem.
> 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
> Assignee: Scott M Stark
> Fix For: JBossAS-3.2.7 Final
>
> Original Estimate: 3 hours
> Remaining: 3 hours
>
> 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
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development
