...
It should contain a bean entry for every action in your app and these beans should be defined as singletons. The bean names in action-servlet.xml must match a corresponding action path in the action-mappings section of your struts-config.xml. So for instance, in the oas-skeleton, the bean name="/EnterSearchCriteria" in the action-servlet exactly matches the action path="/EnterSearchCriteria" in the struts-config and they both refer to one of the three actions you will find in the oas-skeleton (edu.mit.oasskeleton.controller.action.EnterSearchCriteriaAction).
Your You won't make any changes to the bean name "/EntryAction" and most apps will have only one entry point, in which case, you won't create any additional entry actions. But your app can have any number of entry points. Each of the entry points would have an action that is configured in struts-config to be chained to an action-servlet bean name that uses the class edu.mit.mortar.controller.action.GlobalEntryAction. However, these bean names 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 oas-skeleton which comes with all new projects set up by the IDD Team. In this example there is a single entry point, /EntryAction, which is configured to chain to a specific action (<forward name="Chain" path="/EnterSearchCriteria.do" redirect="true"/>) to the action, EnterSearchCriteria, in the struts-config.xml file.
...