I agree that the API is terrible. Is anyone coming up with a better idea for Xwork?
Blake ----- Original Message ----- From: "Rickard" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, December 21, 2002 4:39 AM Subject: Re: [OS-webwork] PropertyEditor cache > Heng Sin Low wrote: > > > I remember seeing in a previous post in the list that PropertyEditor is being > > cache inappropriately in BeanUtil ( not thread safe, I think ). I don't see > > anything related to that in the 1.3 changelog or do I miss something here ( Not > > an issue after all, may be ) ? > > > Caching PropertyEditor's is not the solution. The solution is to not use > PropertyEditors at all. They weren't designed for what we use them for, > and the API is just terrible. > > /Rickard > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: Order your Holiday Geek Presents Now! > Green Lasers, Hip Geek T-Shirts, Remote Control Tanks, Caffeinated Soap, > MP3 Players, XBox Games, Flying Saucers, WebCams, Smart Putty. > T H I N K G E E K . C O M http://www.thinkgeek.com/sf/ > _______________________________________________ > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > > > ------------------------------------------------------- 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
