> would be great if you could somehow send the decoupled > version.
I will have to look in my past email to see if I can find it. > I only need to write one Default class for all the > screens and > just rewrite the isAuthorized method to call the tool, right? Correct. As I look back it may have made more sense to do the auth calls from within a custom SessionValidator. However, the quickest route is the "One Screen" technique you mentioned above. I would also suggest creating a parent Action class to inherit from that does the same thing. You will obviously have to write the individual actions to accomplish your needs, however, you should be able to define the isAuthorized() method once in the parent Action class. Scott > -----Original Message----- > From: Akmal Sarhan [mailto:[EMAIL PROTECTED]] > Sent: Monday, June 03, 2002 12:03 PM > To: [EMAIL PROTECTED] > Subject: RE: Security framework > > > Thanks Scott, > would be great if you could somehow send the decoupled > version. I had a > quick look and think it is really handy and cool, so if I understand > correctly, I only need to write one Default class for all the > screens and > just rewrite the isAuthorized method to call the tool, right? > regards > Akmal
