|
From: Seth L. <se...@eh...> - 2004-06-23 02:29:52
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alef Arendsen wrote: | I think it's a good idea to decouple the handlermappings from the | interceptors. I don't think it's such a huge refactoring. Juergen, could | you shed your light on the following: | | - refactoring of AbstractHandlerMapping into AbstractMapping, factoring | out functionality used for both AbstractHandlerMapping and | AbstractInterceptorMapping | - subclass of AbstractMapping: AbstractUrlMapping, responsible for URL | related stuff (including PathHelper) | - subclasses: AbstractUrlInterceptorMapping and | AbstractUrlHandlerMapping | | From there on the old hierarchy for handler mappings can continue, | interceptor structure could be the same. We don't really need to change | anything to the HandlerExecutionChain AFAIK. | | Opinions? The more I think about this, the more I think it will be useful. For instance, I'd like to have the OpenSessionInViewInterceptor to apply to everything (/*) where other Interceptors apply to certain Controllers. I'm starting to get a proliferation of UrlHandlerMapping objects just to map different combinations of Interceptors. Jurgen, any more thoughts on this? I might even implement this one soon because it will greatly simplify things. Thanks, Seth -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3-nr1 (Windows XP) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFA2OseKZsFSwtW+wIRAm96AJ48uc9AfJ1AO6KTA7hx0OIy+IA/HQCggVpG Qvwdm8Kqp0iITFuRY6bOW6Q= =RNla -----END PGP SIGNATURE----- |