DO NOT REPLY [Bug 15969] - Ability to use TilesRequestProcessor even if it not initialized from TilesPlugin

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=15969>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=15969


mrdon@twdata.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |WONTFIX




------- Additional Comments From mrdon@twdata.org  2004-12-22 03:13 -------
I'm closing this ticket as the new ComposableRequestProcessor allows the request
process handling to be easily extended and will work for tiles and non-tiles apps.

Besides, this issue can be mitigated with Struts 1.2 by creating an
RequestProcessorHelper which contains all the RequestProcessor methods you want
to customize, but doesn't extend RequestProcessor.  Then, just create two
RequestProcessors and have their method implementation delegate to your
RequestProcessorHelper.  Create a plugin that runs after the Tiles plugin, which
looks at the configured RequestProcessor and loads the correct one.  This way,
while you have some extra code, you have no duplicate business logic.  This
approach is used by stxx (http://stxx.sf.net) to support Tiles and non-Tiles apps.  

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org