struts-config.xml (The Struts Configuration File)
Each of your ActionForms must be configured within the form-beans section of the struts-config.xml. In the example below the oas-skeleton has 3 ActionForms.
Each of your Actions must be configured within the action-mappings section of the struts-config.xml and each action path (e.g., /SearchPeople) must exactly match a bean name within action-servlet.xml. It is the bean name within the action-servlet.xml (e.g., /SearchPeople) that maps the bean name to the actual Action(e.g., SearchPeopleAction).
For each Action that accepts input from the user, there should be an ActionForm (e.g., SearchCriteriaForm) attached to its associated action path (e.g., /SearchPeople). If the input is going to be validated via the Struts Validator Framework a jsp/tile (e.g., oasskeleton.enter_search_criteria) to go back to in case of errors should be specified via the action input attribute. This is a good place to talk about scope.
The struts-config.xml is also where /EntryAction is configured to chain to one of your Actions (e.g., the Action associated with the bean name /EnterSearchCriteria). Your app can have multple entry points. Each of these should be like the /EntryAction example below and their action-servlet bean name/ struts-config bean path must be in the format XXXEntryAction (where XXX is some name you choose), otherwise the session restart mechanism will cause your app to loop infinitely.
For actions that don't need input (hidden or visible), they should not have a form.