In my opinion, you should avoid using custom interceptor stacks whenever possible. That way, you can simplify your configuration and make your application more consistent. If the mailreader always used the default stack, the zero configuration conversion would be trivial.
Of course, another equally valid style is to use custom interceptor stacks on most every action/package, but it does make zero configuration adoption more difficult. Don On 3/16/07, Dave Newton <[EMAIL PROTECTED]> wrote:
--- Ted Husted <[EMAIL PROTECTED]> wrote: > If anyone is looking for something to do, a > Zero-Configuration MailReader would make a world of > difference right now. I know I'm not a committer, but I have one more free weekend before a new gig starts and I was all set to volunteer... But then I started looking at it and I'm not sure how the interceptor bits would work--I don't see any annotations for defining interceptors. So I know this belongs on the user list, but I almost volunteered, so I'll be a dork and ask how that would be handled by a real developer. Dave ____________________________________________________________________________________ Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. http://farechase.yahoo.com/promo-generic-14795097 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
