> -----Original Message----- > From: Trevor Squires [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 13, 2003 4:21 AM > To: Webwork List > Subject: Re: [OS-webwork] can't grok XWork Result workings > > > > Yowch. > > I think I've figured out what the 'magic' was. It would > appear that there is only once instance for each class of an > interceptor. > > This is pretty counter-intuitive to me as interceptors are > defined on a per-package basis in the xml config file. > > Not only that but won't the AbstractInterceptor.result get > clobbered across threads? > > This doesn't seem right... > > Trevor
Yes, you're right. Good Catch. For now, I'm making the interceptors go back to being completely stateless by removing the result string from the instance and instead passing it to the after() call. It's on my to-do list to look at Interceptors again... I still think, until someone can show me an example, that Interceptors should be stateless and don't need parameterization, so we can stick with the one instance per class. Jason ------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
