> As for now, i have put the basic stuff there like finding a > forward for a database faillure and so on..
I handle failures like this using the declarative exception handling (<global-exceptions>). One less thing I have to code in my Actions. > (like in the mailreader example by the way). Also, i have put > a method that retrieves a handler from the servlet context > that all actions need. Is this a good idea? > > I wonder whether it's a good idea to do authorization in the > base class by implementing an abstract execute method that > will check whether a user is logged in.. All action classes > then will first call this abstract execute method. I do this in a custom subclass of RequestProcessor (override processActionPerform()). Check the Javadoc for this class and you will see that you have access to everything that Action has and you have the added benefit of keeping your Actions more "pure". Also, I can use various types of actions instead of being tied to just Action or MappingDispatchAction (whichever variant you choose as your base class). > > What do you put in base classes? > Thanks --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
