Hi there, When implementing the new "BeanUtil" replacement it would be good if it could allow you to also specify parse formats on a global (static) level as well.
This is possible with the current implementation by registering my own PropertyEditors with the PropertyEditorManager class. I use this today in order to override several of Webworks property editors for example DateEditor and different number editors. It is good because I can then: - Use one standard dateeditor throughout my application. That editor supports the different date formats that my customer wants to allow. The dateformat does not necessary have to follow a standard but can be any format the customer prefers. - Have localised/customised error messages generated from my property editors, for example when input in a date or number field is not valid (not parseable). - I do not have to clutter my code by creating alot of BeanInfo classes, unless I really need it. So it would be nice if the new implementation would allow something similar as well. Best regards, Dick Zetterberg [EMAIL PROTECTED] ----- Original Message ----- From: "Patrick Lightbody" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, October 31, 2002 1:44 AM Subject: [OS-webwork] Ognl status > > In the meantime, maybe > ditching PropertyEditors but coming up with our own (FAST) BeanUtil > implementation that doesn't use PropertyEditors would be best. It shouldn't > need to be very complex. The main things we need are: > > - complete data conversion for both setting and getting data > - ability to write our own data converters for each webwork action (not > class) > ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
