Hi There, I encounter a strange Tomcat (6.0.14) behavior. When deploying my Tapestry web-application (5.0.13), Tomcat tells me that pages are not available unless I specify the root-page without context first. Just an Example to be more illustrative:
1. Deploy myApp 2. Visit Page /myApp/view/12345 -> Tomcat: Resource not Found (12345 is A document ID in this example and becomes the activation-context) 3. Visit Page /myApp/view/ -> Found 4. Visit Page /myApp/view/12345 again -> Found and the correct document is send Why do I have to use the exact page path without context to 'initialize'(?) The page before using it with context? Has anyone seen such thing before? My local tomcat does not behave this way. Any Ideas where to look at? Cheers, Martin (Kersten) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
