[
https://issues.apache.org/struts/browse/STR-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45035#action_45035
]
Paul Benedict commented on STR-3168:
------------------------------------
The resultant work:
* Introduce new org.apache.struts.dispatcher package
* Introduce new Dispatcher interface
* Retrofit ActionDispatcher with Dispatcher interface
* Introduce new ExecuteDispatcher command into the controller that marshalls a
standard set of responses
* Add dispatcher attribute to the action configuration
> Add dispatching support to Controller and Action configuration
> --------------------------------------------------------------
>
> Key: STR-3168
> URL: https://issues.apache.org/struts/browse/STR-3168
> Project: Struts 1
> Issue Type: New Feature
> Components: Core, Extras
> Reporter: Paul Benedict
> Assignee: Paul Benedict
> Fix For: 1.4.0
>
>
> Based on the discussions of STR-2940 and the general trend of the industry,
> the correct place for a framework to support dispatching is not in the
> Action, but as part of the Controller. The Action can do anything it wants
> once it has the request, but the support belongs to the framework.
> See also http://www.theserverside.com/patterns/thread.tss?thread_id=21854
> The following changes are proposed:
> * Introduce a Dispatcher interface that accepts the current ActionContext and
> returns an Object
> * Add @dispatch to the <action> element
> * Either modify ExecuteAction or create subclass that executes the action by
> delegating to the Dispatcher interface
> * Object is then marshalled into an ActionForward through a conversion process
> * Retrofit ActionDispatcher with the interface
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
