The theory is to compose your own request processor, but has anyone got a working example of such a beastie (yet)?
Well, I'm not sure what you mean, but I have a production app which includes eight locally developed commands interspersed among the standard chain commands. These are responsible for instantiating and populating our "ActionContext" class (similar to some things we've discussed here recently), deriving the user ID from a variety of possible authentication sources, establishing the user's session based on the authenticated ID, enforcing access control rules, and executing our "view controller" code before dispatching to the requested view.
A chain based RP made throwing in each of these in its place extremely simple, while adding each of these in the appropriate place by extending any other RequestProcessor class would have been extremely cumbersome.
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
