commons-beanutils:commons-beanutils

Create release tag for Apache Commons BeanUtils release 1.10.1.

Create release tag for Apache Commons BeanUtils release 1.10.0.

• [BEANUTILS-458] BaseLocaleConverter.checkConversionResult() no longer throws a ConversionException if the result of a conversion is null.

• [BEANUTILS-456] For PropertyDescriptors obtained via custom introspection now additional information is stored to prevent that write methods are lost during garbage collection.

Apache Commons BeanUtils 1.9.0 Release Notes

Release 1.9.0 contains some bug fixes and improvements that have accumulated after the 1.8.3 release. The most obvious change is that the new version now requires JDK 1.5 or higher, and that language features introduced with Java 5 (mainly generics) are used. A new feature has been introduced, too: the support for customizing bean introspection.

• [BEANUTILS-454] BeanUtilsBean.copyProperties() no longer throws a ConversionException for null properties of certain data types. This fixes a regression introduced in version 1.8.0. The issue is related to [BEANUTILS-387].
• [BEANUTILS-411] BeanUtilsBean.setProperty throws IllegalArgumentException if getter of nested property returns null.
• [BEANUTILS-408] MethodUtils.invokeMethod() throws NullPointerException when args==null.
• [BEANUTILS-426] ConstructorUtils.invokeConstructor(Class klass, Object arg) throws NullPointerException when arg==null.
• [BEANUTILS-380] BeanMap methods should initialize the root cause of exceptions that are thrown when running on JDK 1.4+.
• [BEANUTILS-379] Remove copied Collection classes.
• [BEANUTILS-378] BeanMap does not work in osgi (fixed by BEANUTILS-378).
• [BEANUTILS-381] MethodUtils getMatchingAccessibleMethod() does not correctly handle inheritance and method overloading.

Adding generics to the BeanUtils API has been done in a backwards compatible way. This means that after type erasure the resulting classes look the same as in the previous version. A drawback of this approach is that sometimes it is not possible to use the logically correct type parameters because then backwards compatibility would be broken. One example is the BeanMap class: The class is now a Map<Object, Object> while its keys actually are strings. However, implementing Map<String, Object> would change the signatures of some methods in an incompatible way. More details about limitations of the generification can be found at https://issues.apache.org/jira/browse/BEANUTILS-452

One exception from the compatibility rule is the ResultSetIterator class which now implements the Iterator<DynaBean> interface. This causes a change in the return value of its next() method. ResultSetIterator is used internally as the iterator implementation within ResultSetDynaClass (it is probably a mistake that it is public). So chances are minimal that this change affects existing code.

Another change which may affect compatibility is [BEANUTILS-379] (details can be found at https://issues.apache.org/jira/browse/BEANUTILS-379). Older versions of BeanUtils contained some classes that were copied from Commons Collections. These classes have now been removed, and a dependency to Commons Collections has been added; the collections jar now has to be contained in the classpath, too.

Except for the change on ResultSetIterator and the additional dependency to Commons Collections, Commons BeanUtils 1.9.0 is fully binary compatible with the previous version 1.8.3.

BeanUtils 1.8.3 is binary compatible release with Beanutils 1.8.2, containing only bug fixes.

BeanUtils 1.8.3 requires a minimum of JDK 1.3.