Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Wed, 7 Jan 2015 09:38:34 +0000 (UTC)
From: "Sven Raddatz (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12765337.1420623502000.26994.1420623514436@Atlassian.JIRA>
In-Reply-To: <JIRA.12765337.1420623502000@Atlassian.JIRA>
References: <JIRA.12765337.1420623502000@Atlassian.JIRA>
 <JIRA.12765337.1420623502907@arcas>
Subject: [jira] [Created] (BEANUTILS-473) Backward compatibility - copying
 null values to primitive types
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Sven Raddatz created BEANUTILS-473:
--------------------------------------

             Summary: Backward compatibility - copying null values to primitive types
                 Key: BEANUTILS-473
                 URL: https://issues.apache.org/jira/browse/BEANUTILS-473
             Project: Commons BeanUtils
          Issue Type: Bug
          Components: Bean / Property Utils
    Affects Versions: 1.9.2
            Reporter: Sven Raddatz


Copying a NULL value to a primitve property in destination bean (e.g. boolean) was silently ignored in BU 1.7.0. In 1.9.2 this is throwing an IllegalArgumentException. 

Since converters are not executed when value is null there is no way to prevent this behaviour, making it hard to migrate from 1.7.0 to 1.9.2. The only way to accomplish this task is to switch from primitive to non-primitive types in all destination beans, which would result in huge testing effort. 

It would be nice to either have the possibility to use convertes to handle null values with a valid default (e.g. null = false in case of boolean) or to globally have a switch for a "silent / lenient mode" where any exceptions during copying are silently ignored. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)