Thanks for your reply. >> Is there a more elegant way of solving this problem other than to add more >> extended classes each time and duplicate the code?
> Have you considered a Servlet Filter for the authentication part? A good idea, unfortunately we are still using Websphere v4.x which doesn't support the Servlet API v2.3. > And the 'generic functionality' might be able to be moved out into 'Helper' > classes rather than put directly into the Actions. Yes, could do, but I like the idea of having a "base" Action class. It also seems to be the recommended approach, e.g. from Struts In Action "Always create a base class for the custom Actions in your application." Thanks again. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
