As I understand it, Struts2 action class instances can (unlike Struts1) be stateful, because each GET or POST to an action creates a new instance of the backing action class.

I also see that there's a standard(?) idiom (Pattern?) to provide input forms: the same .jsp is used as the View component of two different actions, like this:

```
<action name="showForm" class="defaultActionThatDoesNothingExceptReturnSuccess">
  <result name="success">inputForm.jsp</result>
</action>

<action name="validateAndProcessForm" class="realAction">
  <result name="input">inputForm.jsp</result>
  <result name="success">formProcessed.jsp</result>
</action>

```

The first action just displays the form, without validating the input or processing it. The form in the .jsp posts to the *second* action:

```
<s:form action="validateAndProcessForm" method="post">

```

and that second action validates the posted fields/parameters, returning "input" if the form's inputs are incomplete or invalid, or actually calling the action class's `execute` if the inputs are complete and valid, thus processing the form and returning the (*e.g.*) `formProcessed.jsp` that displays something like "thanks for your input!".

So we have this sort of "picket fence" idiom:

```
defaultAction-           -> realAction-
             |           |     |       |
             -> input.jsp-  <---       -> success.jsp

```

This is done so that the first time `input.jsp` is displayed, validations aren't called (and so validation errors are not shown), but that after the submit button on that jsp is clicked, the "real" action will validate the input, possibly passing back errors calling out invalid input which the `input.jsp` will display. 

Which brings us back to stateful, non-singleton actions; because the action is stateful and thus not shared across GETs or POSTs, and each instance is instantiated just for that GET or POST, the action has no way to know if a particular session has "GETted" the same page multiple times. So GETting `showForm.action` will *never* validate, and GETing `validateAndProcessForm` will *always* validate (and show errors if the parameters are invalid), *even if* that GET is the first time a particular session has "GETted" that URL.

Which is why we need the "fence post": the first action just to display the form, the second to capture the input.

Is my understanding correct? Is there a less verbose way to do this, to not validate input on the initial GET, but to validate on the POST, without having to have two actions for every form?