[
https://issues.apache.org/jira/browse/SANDBOX-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15007178#comment-15007178
]
Benedikt Ritter edited comment on SANDBOX-501 at 11/16/15 7:30 PM:
-------------------------------------------------------------------
Hello Matt,
bq. I was wondering if we might have a dialogue concerning commons-beanutils2
in the somewhat near future.
Of corse, I'm always interested in feedback.
bq. Maybe a chat so we can have a back and forth in real time?
The best place for discussions around component design is the development
mailing list. Please forgive me, if I don't respond within a day. I have time
slots of varying length to work on ASF code and BeanUtils2 is not my top
priority at the moment (for example commons-lang3 need a new release)
bq. I'd also like to explore a way to provide optional support for Java 8
features without actually requiring Java 8.
Commons is very conservative when it comes to the Java versions we support. A
lot of the components is still on Java 6. Sandbox components can be developed
rather freely. This is, why I'd like to use BeanUtils2 to explore how APIs can
be designed with the new features.
Again, thank you for your interests in Apache Commons!
Regards,
Benedikt
was (Author: britter):
Hello Matt,
bq. I was wondering if we might have a dialogue concerning commons-beanutils2
in the somewhat near future.
Of corse, I'm always interested in feedback.
bq. Maybe a chat so we can have a back and forth in real time?
The best place for discussions around component design is the development
mailing list. Please forgive me, if I don't respond within a day. I have time
slots of varying length to work on ASF code and BeanUtils2 is not my top
priority at the moment (for example commons-lang3 need a new release)
bq. I'd also like to explore a way to provide optional support for Java 8
features without actually requiring Java 8.
Commons is very conservative when it comes to the Java versions we support. A
lot of the components is still on Java 6. Sandbox components can be developed
rather freely. This is, why I'd like to use BeanUtils2 to explore how APIs can
be designed with the new features.
> Add configurable type conversion support
> ----------------------------------------
>
> Key: SANDBOX-501
> URL: https://issues.apache.org/jira/browse/SANDBOX-501
> Project: Commons Sandbox
> Issue Type: New Feature
> Components: BeanUtils2
> Reporter: Benedikt Ritter
> Attachments: commons-beanutils2.2015-11-13.patch,
> commons-beanutils2.2015-11-14.patch, commons-beanutils2.2015-11-15.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
(v6.3.4#6332)
