In the filter mapping declaration of the Tapestry application add some
dispatchers like this:
filter-mapping
filter-nameapp/filter-name
url-pattern/*/url-pattern
dispatcherFORWARD/dispatcher
dispatcherREQUEST/dispatcher
/filter-mapping
This worked for me.
This is my first exposure to using dispatchers. Found some useful info
here:
http://blog.thomas.heute.name/2008/07/servlet-filter-doesnt-work-or-does-it.html
On Thu, Jul 31, 2008 at 10:22 AM, Hugo Palma [EMAIL PROTECTED] wrote:
In the filter mapping declaration of the Tapestry application add
/T5%3A-RequestDispatcher-to-include-Tapestry5-Pages-tp472602p473541.html
Sent from the Tapestry Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
. (tried
dispatcherINCLUDE/dispatcherdispatcherFORWARD/dispatcher in the t5
filter mappings in web.xml)
Any solutions would be greatly helpful in moving to Tapestry 5.
--
View this message in context:
http://n2.nabble.com/T5%3A-RequestDispatcher-to-include-Tapestry5-Pages-tp472602p472602.html
