commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhaniag (JIRA)" <>
Subject [jira] [Commented] (BEANUTILS-473) Backward compatibility - copying null values to primitive types
Date Fri, 29 Jul 2016 12:00:23 GMT


dhaniag commented on BEANUTILS-473:

Found the same issue in commons-beanutils-1.9.0.jar, commons-beanutils-1.9.1.jar and  commons-beanutils-1.9.2.jar.
But it is working up to  commons-beanutils-1.8.3.jar

> Backward compatibility - copying null values to primitive types
> ---------------------------------------------------------------
>                 Key: BEANUTILS-473
>                 URL:
>             Project: Commons BeanUtils
>          Issue Type: Bug
>          Components: Bean / Property Utils
>    Affects Versions: 1.9.2
>            Reporter: Sven Raddatz
>              Labels: IllegalArgumentException, backwards-compatibility, null-values
> 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

View raw message