Daniel Fagerstrom wrote: > Seem like a good solution to me. I would prefer putting this > functionality in a ShieldingBlockServlet that extends the BlockServlet > though. If we put to much extras in the BlockServlet it will be hard for > people to understand what it does and to contribute to make it stable. > Hmm, yes, you're right - what about using Spring's AOP functionality for this? The problem with sub classing for a functionality is that you might end up with a big set of sub classes for all possible combinations.
Carsten -- Carsten Ziegeler - Chief Architect http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
