Ok nevermind, I thought it was possible. But after I tried writing the code I realized there is no way to distinguish whether or not they explicitly set the value on the annotation to override the default (be it from the annotation itself or web.xml) w/o using null.
Just set the default to true, and if you don't want a field trimmed set it's annotation to false... I think that is fine, and would be preferred by most new people. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Freddy D. Sent: Thursday, May 01, 2008 3:43 PM To: [email protected] Subject: Re: [Stripes-users] Need feedback John, > It would also be if in web.xml you could set a filter param called > trimByDefault = false if you wanted. Mention that that in the release notes > in > case anyone would want to stick with the old way. That won't work. Reread Ben's original message for an explanation of why. Cheers, Freddy ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
