ExceptionPresenter is the appropriate "hook" for any kind of exception related logic.
I see what you mean about a parameterIndex for the StrategyFactory. On 6/14/06, James Carman <[EMAIL PROTECTED]> wrote:
All, Is ExceptionPresenter the best place to put generalized exception-handling logic? I have an idea to refactor it even further than making it a pipeline. It could be even better if we could make the endpoint of the pipeline a "strategy" using HiveMind's StrategyFactory (hivemind.lib module). We'd need to beef it up a bit, because it uses the type of the first method argument to find the appropriate strategy to use and ExceptionPresenter's first argument is IRequestCycle. We need to allow the "parameterIndex" to be customized. The overall ExceptionPresenter service point would still be a pipeline, but the terminator would be a service point which is a strategy-based service. The default strategy for Object (the catch-all) would probably be what it does now. That would allow folks to hook in a strategy for Throwable to short-circuit it. What do you think? James --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com
