To borrow a JSF term, what about ViewHandler? :)
Don
Martin Cooper wrote: <snip />
OK, I hadn't thought about taking it that far. ;-) So this thingumajig would effectively do what PerformForward and PerformInclude do now (or what used to be doForward() and doInclude() in the old request processor), right? And the Tiles version would do more or less what TilesPreProcessor does now?
I think that could be pretty cool, and unless I'm mistaken, it would mean that plugging Tiles into Struts would require only (a) loading the Tiles defs, and (b) registering a thiingumajig, both of which would happen at startup time, and neither of which would involve modifying the request processor. Maybe I'm missing something, but that seems much cleaner than what we have now.
We'd need to figure out what kind of registration mechanism we want. My first thought was to have Tiles call a registerThingumajig() method, but I think we'd want to allow for control over the order in which thingumajigs get a chance to play in the game. This seems like a natural for Chain (give each thingumajig in the chain a chance to play until one says "I got it"), but maybe I've got chain on the brain...
I've been calling this new thing a "thingumajig" here because I don't think "path resolver" or "path handler" (or "path ${foo}") really captures what it does. It's kinda like "OK, take it from here" as far as Struts goes. I don't have any great ideas on what to call that right now.
-- Martin Cooper
Don
-- Martin Cooper
If you put your .tiles paths all under /WEB-INF/ then wouldn't you achieve the same kind of protection that people who put JSPs there do? It seems like that should work, although that's pure speculation.
Joe
-- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
