...
- The method edu.mit.mortar.controller.action.GlobalEntryAction.execute is called and a session is created and the following session attributes are set:
- GlobalKeys.SAP_SYSTEM_ID
- GlobalKeys.WAS_SYSTEM_ID
- GlobalKeys.WAS_HOST
- GlobalKeys.USER_HOME
- Your action (which has been configured to chain after /EntryAction) is called which immediately calls the method IDDAction.execute which sets the following session attributes:
- GlobalKeys.CERT
- GlobalKeys.USERNAME
- GlobalKeys.KERBID
- At the end of IDDAction, SAPBaseAction.doProcess is called which opens a connection to SAP.
- At the end of SAPBaseAction, your action's method doAction is called within a MessageRuntimeException try catch.
- If your action's method doAction calls a SAP RFC, SAPServiceSupport.execute is called.
- If an error message is returned from the SAP RFC at this point, processing will stop and the user will either stay on the same page displaying the error message if an action input has been defined with the current jsp correctly in the struts-config or they will be sent to the GlobalKeys.FAIL jsp page with a MessageRuntimeException unless your action intercepts the MessageRuntimeException and handles it. BAPI Exceptions . In the rare case that you don't want to stop processing and display the error message you should wrap your service call in a try...catch statement intercepting any MessageRuntimeException messages.
BAPIExceptions will be sent to the GlobalKeys.FAIL jsp page.
...