RE: [OS-webwork] Converters need to be unified

[Jason Carreira]

Title: Message

Cool... now we need i18n localized validators.... if we switched from using the property files directly to using ResourceBundle's we could do this pretty easily...   We also need to work on getting conversion to add field messages if it fails... -----Original Message----- From: Pat Lightbody [mailto:[EMAIL PROTECTED] Sent: Thursday, October 02, 2003 12:31 AM To: [EMAIL PROTECTED] Subject: Re: [OS-webwork] Converters need to be unified Well -- there is xwork-default-conversion.properties and xwork-conversion.properties. So xwork-default-conversion.properties is in xwork.jar and then you can write your own xwork-conversion.properties that can override that.   -Pat ----- Original Message ----- From: Jason Carreira To: [EMAIL PROTECTED] Sent: Monday, September 29, 2003 11:25 AM Subject: RE: [OS-webwork] Converters need to be unified The xwork-default-conversion.properties does this, to some extent... Pat, it might be nice to be able to register other default conversion properties files (app specific)... -----Original Message----- From: Fred Lamuette [mailto:[EMAIL PROTECTED] Sent: Monday, September 29, 2003 3:33 AM To: [EMAIL PROTECTED] Subject: [OS-webwork] Converters need to be unified I think WW2 should give the ability to use converters (default and user-defined) easily from actions and views, from a unified entry point. It would be nice. Richard.