You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Sing Li (JIRA)" <de...@geronimo.apache.org> on 2005/06/04 16:21:42 UTC
[jira] Created: (GERONIMO-662) Cannot find root context when app deployed without geronimo-tomcat.xml
Cannot find root context when app deployed without geronimo-tomcat.xml
----------------------------------------------------------------------
Key: GERONIMO-662
URL: http://issues.apache.org/jira/browse/GERONIMO-662
Project: Geronimo
Type: Bug
Components: Tomcat
Versions: 1.0-M4
Environment: WinXP Pro SP1, SUN Java VM 1.4.2_-07-b05
Reporter: Sing Li
Priority: Minor
Attachments: patch.txt
By default, deploying a WAR or EAR without a geronimo-tomcat.xml results in the use of a default deployment plan.
The web.xml webapp id, or the base archive file name is used as a configuration id, and also for the root context. This is consistent with Jetty and OpenEJB behavior, and an ease-of-use feature by design.
A minor bug during the creation of the default plan, in TomcatModuleBuilder.java, prevents the root context from being created properly. The attached patch should fix this.
--
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
[jira] Updated: (GERONIMO-662) Cannot find root context when app deployed without geronimo-tomcat.xml
Posted by "Sing Li (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-662?page=all ]
Sing Li updated GERONIMO-662:
-----------------------------
Attachment: patch.txt
Adds leading "/" to root context of default plan.
> Cannot find root context when app deployed without geronimo-tomcat.xml
> ----------------------------------------------------------------------
>
> Key: GERONIMO-662
> URL: http://issues.apache.org/jira/browse/GERONIMO-662
> Project: Geronimo
> Type: Bug
> Components: Tomcat
> Versions: 1.0-M4
> Environment: WinXP Pro SP1, SUN Java VM 1.4.2_-07-b05
> Reporter: Sing Li
> Priority: Minor
> Attachments: patch.txt
>
> By default, deploying a WAR or EAR without a geronimo-tomcat.xml results in the use of a default deployment plan.
> The web.xml webapp id, or the base archive file name is used as a configuration id, and also for the root context. This is consistent with Jetty and OpenEJB behavior, and an ease-of-use feature by design.
> A minor bug during the creation of the default plan, in TomcatModuleBuilder.java, prevents the root context from being created properly. The attached patch should fix this.
--
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
[jira] Closed: (GERONIMO-662) Cannot find root context when app deployed without geronimo-tomcat.xml
Posted by "Jeff Genender (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-662?page=all ]
Jeff Genender closed GERONIMO-662:
----------------------------------
Fix Version: 1.0-M4
Resolution: Fixed
Verified this issue. Patch worked...and applied. Thanks to SIng for finding the bug.
> Cannot find root context when app deployed without geronimo-tomcat.xml
> ----------------------------------------------------------------------
>
> Key: GERONIMO-662
> URL: http://issues.apache.org/jira/browse/GERONIMO-662
> Project: Geronimo
> Type: Bug
> Components: Tomcat
> Environment: WinXP Pro SP1, SUN Java VM 1.4.2_-07-b05
> Reporter: Sing Li
> Assignee: Jeff Genender
> Priority: Minor
> Fix For: 1.0-M4
> Attachments: patch.txt
>
> By default, deploying a WAR or EAR without a geronimo-tomcat.xml results in the use of a default deployment plan.
> The web.xml webapp id, or the base archive file name is used as a configuration id, and also for the root context. This is consistent with Jetty and OpenEJB behavior, and an ease-of-use feature by design.
> A minor bug during the creation of the default plan, in TomcatModuleBuilder.java, prevents the root context from being created properly. The attached patch should fix this.
--
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
[jira] Updated: (GERONIMO-662) Cannot find root context when app deployed without geronimo-tomcat.xml
Posted by "Dain Sundstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-662?page=all ]
Dain Sundstrom updated GERONIMO-662:
------------------------------------
Version: (was: 1.0-M4)
Assign To: Jeff Genender
> Cannot find root context when app deployed without geronimo-tomcat.xml
> ----------------------------------------------------------------------
>
> Key: GERONIMO-662
> URL: http://issues.apache.org/jira/browse/GERONIMO-662
> Project: Geronimo
> Type: Bug
> Components: Tomcat
> Environment: WinXP Pro SP1, SUN Java VM 1.4.2_-07-b05
> Reporter: Sing Li
> Assignee: Jeff Genender
> Priority: Minor
> Attachments: patch.txt
>
> By default, deploying a WAR or EAR without a geronimo-tomcat.xml results in the use of a default deployment plan.
> The web.xml webapp id, or the base archive file name is used as a configuration id, and also for the root context. This is consistent with Jetty and OpenEJB behavior, and an ease-of-use feature by design.
> A minor bug during the creation of the default plan, in TomcatModuleBuilder.java, prevents the root context from being created properly. The attached patch should fix this.
--
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