commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew P Mann (JIRA)" <>
Subject [jira] [Commented] (SANDBOX-501) Add configurable type conversion support
Date Sat, 14 Nov 2015 17:38:11 GMT


Matthew P Mann commented on SANDBOX-501:


I think you're probably focused on commons-collections being vulnerable to remote code execution
at the moment, but I was wondering if we might have a dialogue concerning commons-beanutils2
in the somewhat near future. Maybe a chat so we can have a back and forth in real time? I
think we can start with the many areas upon which we agree and seeing about committing those
changes without further ado. I'd also like to explore a way to provide optional support for
Java 8 features without actually requiring Java 8. This might be accomplished by grouping
the Java 8 stuff in an optional child artifact. I'm also wondering if we might adopt a [service
loader mechanism|] to
register the default converters. I'm currently reviewing the [org.apache.commons.beanutils.converters|]
and will see about adding to beanutils2.


> Add configurable type conversion support
> ----------------------------------------
>                 Key: SANDBOX-501
>                 URL:
>             Project: Commons Sandbox
>          Issue Type: New Feature
>          Components: BeanUtils2
>            Reporter: Benedikt Ritter
>         Attachments: commons-beanutils2.2015-11-13.patch, commons-beanutils2.java8.patch
> BeanUtils1 supports automatic type conversion when setting properties. This should be
added to BeanUtils2. 
> A problem of the implementation of BeanUtils1 is, that the registry of converts is cached
in the BeanUtils class. BeanUtils2 should provide an API for creating new instances of the
o.a.c.beanutils2.BeanUtils with a customized typ conversion registry.

This message was sent by Atlassian JIRA

View raw message