Quoting Mike Cannon-Brookes <[EMAIL PROTECTED]>: > > Yes, I do mean servlet filters. > > How the hell do they work outside the web environment mate? :) > They don't!
> "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? > No, of course not, I'm all for it. I'm just wary of the potential 'abuse' of interceptors. I guess it's a matter of how much rope do you give people to hang themselves with. > 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 ;) > I understand the command pattern, thanks. > 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. > Yep, good point. I don't think we're saying radically different things. I just wanted to bring up the point that writing interceptors is not entirely unrelated to writing vendor specific appserver code. It's handy dandy, but nicer if one could stick to the spec (but sometimes, the spec just isn't good enough, so one uses specific features). ------------------------------------------------------- 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
