That is really weird because the TapestryFilter is supposed to check to see if there is a resource in the file system that matches the url first, before trying to interpret it. If that functionality is really truly broken, then a bug should be filed, and tapestry fixed.
So the first question, are the url correct and pointing to the real files in the filesystem? Davor Hrg wrote: > there are few ways.. > one is to extend tapestryFilter and use that version in web.xml > > Davor Hrg > > On Jan 7, 2008 6:21 AM, Dapeng <[EMAIL PROTECTED]> wrote: >> Hi guys >> >> I have a protected folder /private under the root >> >> but inside the folder i am only going to serve static contents like >> images and pdf >> >> >> >> >> >> but when i try to access the resource >> >> >> >> /myApp/private/images/1.jpg >> >> >> i got an exception saying there is no such page >> >> >> Unable to resolve 'private/images/1' to a known page name. >> >> >> >> >> >> how to bypass the TapestryFilter? >> >> >> juz let the tomcat handle the request as per normal ??? >> >> >> thx >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
