Re: use of pluggable converters in ConvertUtils changes Struts behavior for primitive wrapper properties

2002-04-07 Thread Martin Cooper
at by making it possible to declare this > is what you want. > > Craig > > > On Tue, 26 Mar 2002, Deadman, Hal wrote: > > > Date: Tue, 26 Mar 2002 21:18:03 -0500 > > From: "Deadman, Hal" <[EMAIL PROTECTED]> > > Reply-To: Struts Developers List <

Re: use of pluggable converters in ConvertUtils changes Struts behavior for primitive wrapper properties

2002-04-07 Thread Deadman, Hal
From: "Craig R. McClanahan" <[EMAIL PROTECTED]> To: "Struts Developers List" <[EMAIL PROTECTED]>; "Deadman, Hal" <[EMAIL PROTECTED]> Sent: Saturday, April 06, 2002 8:08 PM Subject: Re: use of pluggable converters in ConvertUtils changes Struts behavior

re-post: use of pluggable converters in ConvertUtils changes Struts behavior for primitive wrapper properties

2002-04-04 Thread Deadman, Hal
Is the change I describe below to way beanutils does primitive wrapper conversions going to be permanent? The addition of pluggable converters in ConvertUtils on 3/18 has changed the way Struts handles empty form fields that map to primitive Wrapper bean properties. For example, the default Integ

use of pluggable converters in ConvertUtils changes Struts behavior for primitive wrapper properties

2002-03-26 Thread Deadman, Hal
I think the addition of pluggable converters in ConvertUtils on 3/18 has changed the way Struts handles empty form fields that map to primitive Wrapper bean properties. The default IntegerConverter uses a default value of Integer(0) instead of null. This is a fairly significant problem because it