...
Your app can have any number of entry points. Each of the entry points would have an action that can just be configured in spring to use the class edu.mit.mortar.controller.action.GlobalEntryAction. However, they must be named XXXEntryAction (where XXX is some name you choose), otherwise the session restart mechanism will cause your app to loop infinitely.
The example below is from the skeleton and comes with all new projects set up by the IDD Team. There is a single entry point, /EntryAction, which is configured in struts-config.xml. There are an additional 3 skeleton actions. In order to properly configure your application you must change these 3 bean names to reflect the actions in your application:
The Search Help actions found in mortar are also configured here.
...