commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexandre Castro Alves (JIRA)" <>
Subject [jira] [Commented] (BEANUTILS-278) Remove copied Collections classes
Date Fri, 15 Jun 2012 14:38:42 GMT


Alexandre Castro Alves commented on BEANUTILS-278:

Is this still being planned?

I am running into a class-loading problem in an OSGi environment because of the duplicate
FastHashMap. In my case, other bundles are importing the FastHashMap from commons.collection
and passing it along as an argument to beanutils, which then collides with the internal copy
of the FasthHashMap.

Can we please take a look at this with some urgency?

You should either import as well from commons.collections or rely only on Map/HashMap, as
in the proposed patch.

> Remove copied Collections classes
> ---------------------------------
>                 Key: BEANUTILS-278
>                 URL:
>             Project: Commons BeanUtils
>          Issue Type: Improvement
>    Affects Versions: 1.7.0
>            Reporter: Niall Pemberton
>             Fix For: LATER THAN 1.8.4
>         Attachments: Beanutils-278-2.patch
> The following 4 Commons Collections classes were copied into BeanUtils so that the dependency
on Commons Collections could be removed (these were included in the BeanUtils 1.7.0 release)
> See the following thread for the original reasoning:
> Recent discussion thread on this issue is here:
> Of the above four classes only FastHashMap is used within BeanUtils (and is part of the
public API) - not sure why the other classes were included, but it may be because downstream
systems such as Struts depend on them (which also removed its Commons Collections when it
moved to BeanUtils 1.7.0). Some (but not all) of the BeanUtils public API which exposes FastHashMap
was deprecated in the BeanUtils 1.7.0 release.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message