What if it fails to convert the value? Will that throw an exception? -----Original Message----- From: Patrick Lightbody [mailto:plightbo@;cisco.com] Sent: Friday, November 01, 2002 11:15 AM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Validation in xwork (Ognl?)
Ognl won't help with validation (maybe we can look at FormProc for something like that), but it will do all levels of type conversion you require. That includes global level, as well as bean level, and even property level. -Pat ----- Original Message ----- From: "Dick Zetterberg" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, November 01, 2002 3:14 AM Subject: Re: [OS-webwork] Validation in xwork (Ognl?) > 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 ------------------------------------------------------- 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 ------------------------------------------------------- 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
