The action is the place to check for valid login, not the JSP.
Yes, this is the way I've been doing it.
Each action must do the check for a valid login, but there are ways to avoid coding the check in every action. One way would be to create a subclass of org.apache.struts.action.Action that does the check and have each of your actions extend this base action.
This sounds like a good idea.
Another way would be to put the logic in a method in a utility class and call the utility method in every action.
At the moment I have foo.mypackage.common- package that holds all kinds of utility stuff for filtering strings/converting dates etc.
Was just wondering is it better to have all the common methods for the webapp in one class or should I seperate the methods to own classes.
I mean like put all the filtering related stuff to one class and login related to another etc.
[ December 22, 2005: Message edited by: Nems Vedek ]