Filters absolutly useless in case of direct mapping to view. Grails as yet have not usefull crosecutting concept solution. Security, logging, use statistics is very hard to implement .
Solution:
Now mapping to view is processed in filter but fulters are called in HandlerInterceptor. Place url mapping rpocessing in HandlerInterceptor with lower order than filters handler interceptor.
Description
Filters absolutly useless in case of direct mapping to view. Grails as yet have not usefull crosecutting concept solution. Security, logging, use statistics is very hard to implement .
Solution:
Now mapping to view is processed in filter but fulters are called in HandlerInterceptor. Place url mapping rpocessing in HandlerInterceptor with lower order than filters handler interceptor.
As now we developing highly dynamic AJAX application. It's almost finished.
In our case application have relatively simple views that do not require controller. We try to use direct URI to View mapping but in this case filters not called. We have considerable logic in our filters and we hate to use empty controllers only for getting filters to work.
Vladimir Konkov added a comment - 27/Jan/08 01:32 AM As now we developing highly dynamic AJAX application. It's almost finished.
In our case application have relatively simple views that do not require controller. We try to use direct URI to View mapping but in this case filters not called. We have considerable logic in our filters and we hate to use empty controllers only for getting filters to work.
I hope to find understanding...
Bug
Resolved
Critical
Filters do not called in case of direct mapping to view
In our case application have relatively simple views that do not require controller. We try to use direct URI to View mapping but in this case filters not called. We have considerable logic in our filters and we hate to use empty controllers only for getting filters to work.
I hope to find understanding...