[
https://issues.apache.org/jira/browse/EMPIREDB-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rainer Döbele resolved EMPIREDB-460.
------------------------------------
Fix Version/s: empire-db-3.3.1
Assignee: Rainer Döbele
Resolution: Fixed
completed and tested
> Replace calls to Apache commons.beanutils with own implementation
> -----------------------------------------------------------------
>
> Key: EMPIREDB-460
> URL: https://issues.apache.org/jira/browse/EMPIREDB-460
> Project: Empire-DB
> Issue Type: Improvement
> Components: Core
> Reporter: Rainer Döbele
> Assignee: Rainer Döbele
> Priority: Major
> Fix For: empire-db-3.3.1
>
>
> When working with java beans getting and setting property values is achieved
> through calls to org.apache.commons.beanutils.BeanUtils and PropertyUtils.
> However the implementation is not consistent and BeanUtils.setProperty() does
> not allow to detect whether the property value was really set or whether the
> property does not exist or is read only.
> Hence a new class BeanPropertyUtils should be used throughout Empire-db
> replacing the BeanUtils methods with optimized functionality.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
