On Mon, 29 May 2000, you wrote:
> so, something cool about security of your screens/actions/etc can be easily
> had by simply creating a chain of extends.
Yes, I do this a lot in my Job related applications. Mainly because
I'm lazy. And, it blows people's minds when they look at a class with
about 3-4 lines of code that's checking for login and a given
role/permission.
> This seems totally cool to me. The classes that extend these classes don't
> need to know anything about what is happening behind the scenes...only that
> they are extending base functionality (no need to even call super!). On top
> of it, you can *still* override the isAuthorized() method in the
> implementation screens to do even more security checking
Granularity!
> Wow...totally powerful and totally easy.
I agree! When you look at the amount of code that you're writing and
then you look at the functionality you're getting you realize that
we're doing something right with this WM/Turbine stuff.
Do you plan on adding some example of this kind of stuff in your
ApacheCon presentations?
--
dave
[EMAIL PROTECTED]
----------------------
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
