Coming back on that action level filter discussion I've left here: it's not working/existing in the current codebase, currently FilterAttribute is defined valid only for classes, so you can't compile a controller having a Filter attribute on it's method
I've seen this blog post: http://randomcode.net.nz/2008/03/03/adding-action-filters-to-monorail-controllers/ and I'm looking to get this feature into the main code base, I have some design questions about it: - wouldn't it be preferable to use the same Filter Attribute rather than introducing another one as done in the article? - ActionMetaDescriptor seems to be the right place to have a reference of action level filters, does it feel right to add an ActionLevelFilters member here? - how are dynamic actions expected to deal with filters? should we take care of applying filters that might declared on dynamic actions? should we support it at the class or method level? another question concerning dynamic actions, I would expect these to be handled the same way as controller concerning attributes (return binder, filters, layout overriding, helpers), I think this part is not clear, would it be helpfull to specify what is ok and at which level these attributes have to be defined for dynamic actions? Thanks for your feedback -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
