DO NOT REPLY [Bug 17939] New: - WarpEngine doesn't support defaultHost + patch

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17939>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17939

WarpEngine doesn't support defaultHost + patch

           Summary: WarpEngine doesn't support defaultHost + patch
           Product: Tomcat 4
           Version: 4.1.18
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Connector:Webapp
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: karl@xk72.com


The WarpEngine doesn't use the defaultHost parameter. I would like to use 
defaultHost so that I can activate autoDeploy,liveDeploy,deployXML for the 
WarpConnector hosts without having to configure a separate host for each 
virtual host.

Have patched WarpConfigurationHandler.java to add this functionality:

65a66
> import org.apache.catalina.Engine;
262a264,272
>         if (host==null) {
>         	// Try to use defaultHost
>         	String defaultHost = ((Engine)container).getDefaultHost();
>         	if ( defaultHost != null ) {
>         		host = (Host)container.findChild
(defaultHost.toLowerCase());
> 	            if (Constants.DEBUG)
> 	                logger.debug("Using defaultHost for "+hostName);
>         	}
>         }

This works well on my development server... I'm not sure why new hosts are 
automatically created rather than using a defaultHost scenario in 
WarpConfigurationHandler currently - maybe I'm missing something.

cheers,
k@rl

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org