composable RequestProcessor

[Joe Germuska]

Has anyone else wished that RequestProcessor were more composeable? 
That is, we have come upon a case where we need to override the 
behavior of a single method in RequestProcessor, but we feel a little 
sketchy about closing off our ability to use other tools which 
override RequestProcessor (like Tiles).  Technically, we could just 
extend the TilesRequestProcessor, which works even if you aren't 
using tiles, but that's a stop-gap.

I'm sure other people have thought about how to make the 
RequestProcessor composeable of smaller handlers for each life-cycle 
method...    but I thought I'd see what thoughts were out there 
before riffing on my own ideas.

I "staked out" 
http://nagoya.apache.org/wiki/apachewiki.cgi?RequestProcessor on the 
Wiki as an alternative area for discussion, but of course, if people 
prefer to use the mailing list, I'll be watching...

Joe



--
--
Joe Germuska
[EMAIL PROTECTED]
http://blog.germuska.com
"If nature worked that way, the universe would crash all the time."
        --Jaron Lanier
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]