Agree.  Welcome file list is probably the cleanest (standards-based) fix.  


    <welcome-file-list>
     <welcome-file />
    </welcome-file-list>

This seems to tell Tomcat "there are no welcome files" ...   

In fact, seems like you can set welcome file to any arbitrary component and
it will still pick up Tapestry Index.  

For instance, 

        <welcome-file>index</welcome-file>

Or,


        <welcome-file>about</welcome-file>

Note that there is an about component in newapp - still picks up Index (?!)
- seems like anything here is ignored. 

Or, 

        <welcome-file>Burger King in Moscow</welcome-file>

All of of the above are equivalent.  

However a physical file name with extension, 

        <welcome-file>Bienvenue.jsp</welcome-file>

will work whether or not there is a Bienvenue.jsp (i.e. go to Bienvenue.jsp
if present, failover to Index when not).  

The ONLY filename that generates the error (does NOT failover to Index when
no in system) 

        <welcome-file>index.jsp</welcome-file>

The htm and html extensions to index are OK...meaning failover to Index if
not present just like the "french" verison.

I think we have beaten this to death,  thanks guys.  




--
View this message in context: 
http://tapestry.1045711.n5.nabble.com/Tomcat-7-deployment-TapestryModule-RequestExceptionHandler-Processing-of-request-failed-with-uncaugh-tp5637647p5639153.html
Sent from the Tapestry - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org

Reply via email to