This allows the designation of handler which its processing could result into navigation to the defined path. This restricts navigations to the defined path to going through the handling object and the method, if the latter is included.

 {<handler-object>.callMethod}

Depending on the semantic used on the platform, it could either be construed, that events that are result of invoking the handler object or optionally through its method, would result in navigating to the current path.

Or else, only events that are result of handling by a handler object or optionally through its method, that could navigate to the current path. The earlier is an access rule, whereas the latter aids in flow logic.

For Struts, this entry is used to record the flow logic involved in action processing.

It is the action path that would be entered in this attribute. This would then be part of the action definition.

The method specification has no relevance to Struts configuration; however, this entry could be of use for custom implementation. That is, there is no declarative means for flow logic, based on action method; the logic as provided by Struts is based on action.