Bug 40155 - Context setup for JSPs in 5.5.17
Summary: Context setup for JSPs in 5.5.17
Status: RESOLVED DUPLICATE of bug 39817
Alias: None
Product: Tomcat 5
Classification: Unclassified
Component: Servlet & JSP API (show other bugs)
Version: 5.5.17
Hardware: Other other
: P2 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
Depends on:
Reported: 2006-08-01 19:10 UTC by Eric Sandusky
Modified: 2006-08-01 16:20 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description Eric Sandusky 2006-08-01 19:10:13 UTC
This is a duplicate of Bug 39817 and 40130.  I am resubmitting because I did 
not get an answer to my question.

What is the proper Tomcat configuration for my application in 5.5.17?  I have 
reviewed the online docs and I cannot hit my login page, nor does my 
application run my listeners on startup.  What am I doing wrong, in comparison 
to 5.5.12?

My setup is as follows:

<host name="concept" appBase="D:\webapps\Concept" unpackWARs="true" 

context.xml (under D:\webapps\Concept\ROOT folder)
<context path="" docBase=""/>

Code structure

d:\webapps\Concept\catalog (contains jsps)
d:\webapps\Concept\core (contains jsps)
d:\webapps\Concept\WEB-INF (contains compiled classes/libs)

/core/*.jsp are included properly
/catalog/*.jsp are NOT included properly

What is the difference between those 2 folders?

Tomcat Manager shows a "context" for each JSP folder (catalog, core, etc), in 
addition to /, and other contexts I have created in Catalina/concept folder.  
Why is this different from previous versions?
Comment 1 william.barker 2006-08-01 19:27:15 UTC

*** This bug has been marked as a duplicate of 39817 ***
Comment 2 Remy Maucherat 2006-08-01 23:20:09 UTC
With <host name="concept" appBase="D:\webapps\Concept" unpackWARs="true" 
autoDeploy="true"/>, it should be painfully obvious that Tomcat will attempt to
deploy whatever folders are in your "D:\webapps\Concept" folder as webapps.