You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Brian Pontarelli (JIRA)" <ji...@apache.org> on 2007/09/18 16:56:36 UTC
[jira] Created: (WW-2193) Rework FilterDispatcher to be pluggable
Rework FilterDispatcher to be pluggable
---------------------------------------
Key: WW-2193
URL: https://issues.apache.org/struts/browse/WW-2193
Project: Struts 2
Issue Type: Improvement
Components: Dispatch
Affects Versions: 2.1.x
Reporter: Brian Pontarelli
Currently, the majority of how Struts handles actions, static resources and passing the request down the filter chain is handled in FitlerDispatcher via protected methods. In order to change this functionality, plugins and applications must write their own filter and change their web.xml file to use it.
It would be nice if the FitlerDispatcher was completely pluggable and all of its operations were performed via well defined interfaces. Plugins could then inject different implementations of these interfaces allowing modifications to the main handling of the HTTP request and response.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WW-2193) Rework FilterDispatcher to be pluggable
Posted by "Don Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Don Brown updated WW-2193:
--------------------------
Fix Version/s: (was: 2.1.x)
2.1.3
> Rework FilterDispatcher to be pluggable
> ---------------------------------------
>
> Key: WW-2193
> URL: https://issues.apache.org/struts/browse/WW-2193
> Project: Struts 2
> Issue Type: Improvement
> Components: Dispatch Filter
> Affects Versions: 2.0.10
> Reporter: Brian Pontarelli
> Fix For: 2.1.3
>
>
> Currently, the majority of how Struts handles actions, static resources and passing the request down the filter chain is handled in FitlerDispatcher via protected methods. In order to change this functionality, plugins and applications must write their own filter and change their web.xml file to use it.
> It would be nice if the FitlerDispatcher was completely pluggable and all of its operations were performed via well defined interfaces. Plugins could then inject different implementations of these interfaces allowing modifications to the main handling of the HTTP request and response.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WW-2193) Rework FilterDispatcher to be pluggable
Posted by "Don Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Don Brown updated WW-2193:
--------------------------
Affects Version/s: (was: 2.1.x)
2.0.10
Fix Version/s: 2.1.x
> Rework FilterDispatcher to be pluggable
> ---------------------------------------
>
> Key: WW-2193
> URL: https://issues.apache.org/struts/browse/WW-2193
> Project: Struts 2
> Issue Type: Improvement
> Components: Dispatch
> Affects Versions: 2.0.10
> Reporter: Brian Pontarelli
> Fix For: 2.1.x
>
>
> Currently, the majority of how Struts handles actions, static resources and passing the request down the filter chain is handled in FitlerDispatcher via protected methods. In order to change this functionality, plugins and applications must write their own filter and change their web.xml file to use it.
> It would be nice if the FitlerDispatcher was completely pluggable and all of its operations were performed via well defined interfaces. Plugins could then inject different implementations of these interfaces allowing modifications to the main handling of the HTTP request and response.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (WW-2193) Rework FilterDispatcher to
be pluggable
Posted by "Don Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44254#action_44254 ]
mrdon edited comment on WW-2193 at 6/21/08 8:23 AM:
--------------------------------------------------------
First cut at http://svn.apache.org/viewvc/struts/struts2/trunk/core/src/main/java/org/apache/struts2/dispatcher/filter/ although it doesn't address plugin pluggability...yet....
was (Author: mrdon):
First cut at http://svn.apache.org/viewvc/struts/struts2/trunk/core/src/main/java/org/apache/struts2/dispatcher/filter/
> Rework FilterDispatcher to be pluggable
> ---------------------------------------
>
> Key: WW-2193
> URL: https://issues.apache.org/struts/browse/WW-2193
> Project: Struts 2
> Issue Type: Improvement
> Components: Dispatch Filter
> Affects Versions: 2.0.10
> Reporter: Brian Pontarelli
> Fix For: 2.1.3
>
>
> Currently, the majority of how Struts handles actions, static resources and passing the request down the filter chain is handled in FitlerDispatcher via protected methods. In order to change this functionality, plugins and applications must write their own filter and change their web.xml file to use it.
> It would be nice if the FitlerDispatcher was completely pluggable and all of its operations were performed via well defined interfaces. Plugins could then inject different implementations of these interfaces allowing modifications to the main handling of the HTTP request and response.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WW-2193) Rework FilterDispatcher to be pluggable
Posted by "Don Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44254#action_44254 ]
Don Brown commented on WW-2193:
-------------------------------
First cut at http://svn.apache.org/viewvc/struts/struts2/trunk/core/src/main/java/org/apache/struts2/dispatcher/filter/
> Rework FilterDispatcher to be pluggable
> ---------------------------------------
>
> Key: WW-2193
> URL: https://issues.apache.org/struts/browse/WW-2193
> Project: Struts 2
> Issue Type: Improvement
> Components: Dispatch Filter
> Affects Versions: 2.0.10
> Reporter: Brian Pontarelli
> Fix For: 2.1.3
>
>
> Currently, the majority of how Struts handles actions, static resources and passing the request down the filter chain is handled in FitlerDispatcher via protected methods. In order to change this functionality, plugins and applications must write their own filter and change their web.xml file to use it.
> It would be nice if the FitlerDispatcher was completely pluggable and all of its operations were performed via well defined interfaces. Plugins could then inject different implementations of these interfaces allowing modifications to the main handling of the HTTP request and response.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WW-2193) Rework FilterDispatcher to be pluggable
Posted by "Don Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/struts/browse/WW-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Don Brown resolved WW-2193.
---------------------------
Resolution: Fixed
Assignee: Don Brown
I'm going to mark this as done, as it is now possible to compose your own filter by using the operation objects. Not sure how I feel about letting a plugin customize the dispatcher, as you get into strange chicken-egg situations. Please open a new ticket specific to plugin manipulation if you feel it is still necessary.
> Rework FilterDispatcher to be pluggable
> ---------------------------------------
>
> Key: WW-2193
> URL: https://issues.apache.org/struts/browse/WW-2193
> Project: Struts 2
> Issue Type: Improvement
> Components: Dispatch Filter
> Affects Versions: 2.0.10
> Reporter: Brian Pontarelli
> Assignee: Don Brown
> Fix For: 2.1.3
>
>
> Currently, the majority of how Struts handles actions, static resources and passing the request down the filter chain is handled in FitlerDispatcher via protected methods. In order to change this functionality, plugins and applications must write their own filter and change their web.xml file to use it.
> It would be nice if the FitlerDispatcher was completely pluggable and all of its operations were performed via well defined interfaces. Plugins could then inject different implementations of these interfaces allowing modifications to the main handling of the HTTP request and response.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.