...
- Attributes within the XML tag, action
- Each path (e.g., /SearchPeople) must exactly match a bean name within action-servlet.xml.
- Because our types indicate the Spring DelegatingActionProxy, 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).
- name - 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).
- input - If the input is going to be validated either via the SAP RFC or 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 input attribute. If input is not specified, any error messages returned from the SAP RFC will cause a MessageRuntimeException and the user will be sent to the fail page. This is often appropriate on initial screens when there is nothing the user can do to correct the problem but for most other screens the user should stay on the page and correct their input. So input is required in most non-initial action paths.
- 99% of the time scope should be "request" unless there is a need to maintain user entered values between pages (e.g., /SearchHelpNavAction), in which case scope can be "session" but remember to reset the form variables for new entry requests (see mortar's reset method within ActionForm SearchHelpParamsForm).
- Attributes within the XML tag, forward, within the tag, action
- name (e.g., "SearchResultsPage") must exactly match the value sent to ActionMapping's findForward method in the action, which in this example is SearchPeopleAction (e.g., last line of this class is return mapping.findForward("SearchResultsPage")).
- path (e.g., "oasskeleton.search_results") must exactly match a definition name in the tiles-def.xml file.
...