> -----Original Message----- > From: Rickard Öberg [mailto:[EMAIL PROTECTED] > > Ok, well I guess this argument is the same as parameterized > commands. I > have a couple of interceptors in my own AOP application that > are indeed > parameterized, so at least in that context there's a need, and I can > make a similar example for this case (this, interestingly enough, > touches upon the parameterization issues of commands too that I > mentioned in my last post).
Ok, can you implement or describe an interceptor that would need parameterization so we can put it in and use it as a test case? > > Well, mainly the good 'ol curly braces thing (and I have thus > far never > seen a good reason why one would put 'em on the same line), > and also how > portions of the class is delineated. I prefer the template > used in WW, > which had more clearly defined sections. > The curly braces are a religious battle that no-one can ever win :-) The way the class is delineated is a function of the Jalopy template Patrick put in.... You can try to convince him to change it :-) Jason ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
