I was playing around with writing my own IParameterBinder
implementation and ran into some unexpected behavior. It seems that
SmartDispatchController will only ever execute on one implementation
of IParameterBinder. I didn't see any documentation that this was
intentional. I bring this up because it causes custom
IParameterBinder implementions to become rather limited in use if your
team makes use of other implementations (eg ARDatabinder, ARFetch).
For a custom attribute to work with the data binders I must either re-
implement the binders functionality, or extend their classes. Is this
intentional or just an oversight?
If it helps I was spiking out the idea of using an attribute as a
permissions filter along the lines of
public void MyAction([ARFetch][Perm]User user){
//Do something with the user if Perm did not toss a Permissions
Exception, rejecting the currently logged in user
// from accessing this function using the fetched user.
}
I would expect that ARFetchAttribute would execute first, and the
resulting return would be the param that is subsequently passed to
PermAttribute.
--
You received this message because you are subscribed to the Google Groups
"Castle Project Users" 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-users?hl=en.
