commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedikt Ritter (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SANDBOX-472) Transformer Registry
Date Fri, 02 May 2014 10:29:15 GMT

    [ https://issues.apache.org/jira/browse/SANDBOX-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13987565#comment-13987565
] 

Benedikt Ritter commented on SANDBOX-472:
-----------------------------------------

Hello Yogesh,

we will need this functionality in order to make BU2 a substitute for BeanUtils 1. Currently
I'm only having a vague plan on how to implement this. One thing I know for sure is, that
I don't want to have static methods that configure how BeanUtils work. In BeanUtils1 you can
register new Converters using static methods. At the moment I'm thinking about something like
this:

The BeanUtils class will serve like some kind of factory for BeanUtils instances. It provides
a preconfigured BeanUtils instance which has the standard Converts registered. If users need
a custom instance they can use a builder kind of API to create a new instance, which they
can pass around and do stuff with. The standard instance that is registered on the factory
can not be changed to preserve behavior.

So implementing the registry is the second step. First we need to decide how the API for customizing
BeanUtils instances will look like.

> Transformer Registry
> --------------------
>
>                 Key: SANDBOX-472
>                 URL: https://issues.apache.org/jira/browse/SANDBOX-472
>             Project: Commons Sandbox
>          Issue Type: Task
>          Components: BeanUtils2
>    Affects Versions: Nightly Builds
>            Reporter: Yogesh Rao
>             Fix For: Nightly Builds
>
>
> Hi,
> This is my first development JIRA for BU2 so apologies in case i m missing out on basics.
Beanutils1 has a functionality wherein all the converters are registered and are called when
conversion in value is required. This functionality is missing for BU2 project. I also saw
that BeanUtils1 uses WeakFastHashMap for this, which seems like is having issues across architectures
and did see few JIRA's on this. Wanted inputs if having a synchronized instance of WeakHashMap
wrapped in the TransformerRegsitry class and providing methods to register, deregister, restoreDefault,
lookup be desired?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message