geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <...@geronimo.apache.org>
Subject [jira] Closed: (GERONIMO-1036) Tomcat configurations are not relocatable
Date Sat, 01 Oct 2005 20:30:48 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-1036?page=all ]
     
David Jencks closed GERONIMO-1036:
----------------------------------

    Fix Version: 1.0
     Resolution: Fixed

M5: 
Sending        modules/tomcat/src/java/org/apache/geronimo/tomcat/TomcatWebAppContext.java
Sending        modules/tomcat-builder/src/java/org/apache/geronimo/tomcat/deployment/TomcatModuleBuilder.java
Transmitting file data ..
Committed revision 293023.
Head:
Committed revision 293026.



> Tomcat configurations are not relocatable
> -----------------------------------------
>
>          Key: GERONIMO-1036
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1036
>      Project: Geronimo
>         Type: Bug
>     Versions: 1.0-M5
>     Reporter: David Jencks
>     Assignee: David Jencks
>      Fix For: 1.0-M5, 1.0

>
> The tomcat builder is currently inserting a URI into TomcatWebAppContext that contains
the absolute location of the configuration being built.  This means that the configuration
can only be started on a machine in which that location exists and has the expected contents.
> Solution is to save a relative location and resolve it when the WAC is started.

-- 
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


Mime
View raw message