commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Benedict (JIRA)" <>
Subject [jira] Commented: (BEANUTILS-312) Expose the caches in PropertyBeanUtils so they can be controlled if needed
Date Thu, 05 Jun 2008 06:39:45 GMT


Paul Benedict commented on BEANUTILS-312:

Niall, did you consider exposing the caching functionality via an interface?

> Expose the caches in PropertyBeanUtils so they can be controlled if needed
> --------------------------------------------------------------------------
>                 Key: BEANUTILS-312
>                 URL:
>             Project: Commons BeanUtils
>          Issue Type: Improvement
>          Components: Bean / Property Utils
>    Affects Versions: 1.8.0-BETA
>            Reporter: Aaron Zeckoski
>             Fix For: 1.8.0
>         Attachments: beanutils-add-cache-setters-getters-remove-fasthashmap.patch
>   Original Estimate: 1h
>  Remaining Estimate: 1h
> We have an extension to commons beanutils which allows us to make it
> work with public fields as well (and a few other improvements we
> needed like deep cloning). In 1.8.0-BETA it is easier to handle this
> extension (thanks!) but it could be even easier if there was a way to
> get and set the caches which are used for storing the
> PropertyDescriptors. Just switching the type from FastHashMap to Map
> and making a setter and getter which are publicly visible would be
> enough to reduce our the work in extending this significantly.
> The attached patch exposes the caches in PropertyBeanUtils and sets them to be Map instead
of FastHashMap. This also involves a change to PropertyUtils (also changing FastHashMap to
Map). The patch is fairly small and was built again the trunk.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message