| The Remote Proxy Bean is AOP based. You can take any existing advice class and just drop it in in the interceptor names just like ProxyFactoryBean. RemoteProxyBean does set the return type on the methods it creates to ANY. So, you could either throw an exception (which way or may not be viewed as a good idea) or, perform your security in an around advice and return a security error message, as you would in a rest style response. One thing have thought quiet a bit about is creating base Responder objects in Flex which could either provide a default onFault (if we are throwing exceptions) or a method to check for the failed authentication. There are many ways to deal with the actual authentication / security implementation be it session or cflogin, but basically, you should be able to easily get the same functionality as you would with adding the roles attribute to your method. As an aside, the security framework I have worked on for coldspring does optionally use function metadata... C On Apr 20, 2007, at 3:54 AM, Sean Corfield wrote:
|
- [coldspring-dev] Securing Remote Proxy Beans Derek Perez
- [coldspring-dev] Securing Remote Proxy Beans Scott Arbeitman
- [coldspring-dev] Securing Remote Proxy Beans Chris Scott
- [coldspring-dev] Securing Remote Proxy Beans Allen, John
- [coldspring-dev] Securing Remote Proxy Beans Sean Corfield
- [coldspring-dev] Securing Remote Proxy Beans Chris Scott
- [coldspring-dev] Securing Remote Proxy Beans Derek P.
- [coldspring-dev] Securing Remote Proxy Beans Peter Bell
- [coldspring-dev] Securing Remote Proxy Beans Sean Corfield
- [coldspring-dev] Securing Remote Proxy Beans Peter Bell
- [coldspring-dev] Securing Remote Proxy Beans Sean Corfield
- [coldspring-dev] Securing Remote Proxy Beans Lee Howard
- [coldspring-dev] Securing Remote Proxy Beans Chris Scott
- [coldspring-dev] Securing Remote Proxy Beans Lee Howard
- [coldspring-dev] Securing Remote Proxy Beans Kurt Wiersma

