> Yes, I do mean servlet filters. How the hell do they work outside the web environment mate? :)
Again - all of your arguments make some sense. They always do - somewhat ;) You must be thinking about interceptors differently to me. Let me try to make it simple: "I want the ability to run some code before / after defined actions." That would be awesomely useful, for the reasons you mentioned and more. Should you deny me this ability if it does not affect your code? Also, you're drawing a narrow bow to make a point. Noone said 'non-web' is Swing and app clients. That's ONE non-web use, and a rather poor one (as you mentioned - they ain't request / response). I prefer to use Xwork (and we already use WW this way) as a generic command pattern framework. Where? Wherever command pattern makes sense. Go revise your GoF with JoeO - do not pass Go, do not collect $200 ;) What about backend actions? Business logic? Asynchronous messaging like JMS and email? None of these even have a frontend (Swing, HTML or other) but they all work well for the command pattern style of development. > I agree with the pain in the ass to define. So are we saying that the main > advantage of interceptors is that they provide a richer urlpattern? Yes, that is one very large advantage. And they are DIRECTLY tied to Actions. Filters are not, they are tied to actions via actions.xml which is another layer of abstraction (bad for this case). -mike > Quoting Mike Cannon-Brookes <[EMAIL PROTECTED]>: > >> Hani, >> >> Do you mean servlet filters? In which case - surely they don't work at all >> outside a web environment? >> >> And the other problem is that servlet filters are not applied directly to a >> specific action / group of actions, they are URL pattern based? (which is a >> royal pain in the ass to define!) >> >> Mike >> On 13/1/03 10:45 PM, "Hani Suleiman" ([EMAIL PROTECTED]) penned the words: >> >>> Are interceptors really that different from filters? If they are very >>> different, then I'm missing something and you can ignore the rest of this >>> email... >>> >>> However, if they aren't that different, then I believe that they are few >> cases >>> where a interceptor would be required instead of a filter. Filters should >> also >>> be encouraged as they have a far better chance of working if you moved >> outside >>> of a web environment. >>> >>> From hearing examples bandied about here, some people seem to think of >>> interceptors for stuff like security and login, which IMHO is an abuse of >>> them. >>> Thoughts? >>> >>> Hani >>> >>> >>> >>> >>> >>> ------------------------------------------------------- >>> This SF.NET email is sponsored by: FREE SSL Guide from Thawte >>> are you planning your Web Server Security? Click here to get a FREE >>> Thawte SSL guide and find the answers to all your SSL security issues. >>> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en >>> _______________________________________________ >>> Opensymphony-webwork mailing list >>> [EMAIL PROTECTED] >>> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork >> >> >> >> ------------------------------------------------------- >> This SF.NET email is sponsored by: FREE SSL Guide from Thawte >> are you planning your Web Server Security? Click here to get a FREE >> Thawte SSL guide and find the answers to all your SSL security issues. >> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en >> _______________________________________________ >> Opensymphony-webwork mailing list >> [EMAIL PROTECTED] >> https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork >> >> > > > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: FREE SSL Guide from Thawte > are you planning your Web Server Security? Click here to get a FREE > Thawte SSL guide and find the answers to all your SSL security issues. > http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
