commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenneth Xu (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COLLECTIONS-110) [collections] Support parametized classes with commons.collections.
Date Sun, 18 Jun 2006 15:37:35 GMT
    [ http://issues.apache.org/jira/browse/COLLECTIONS-110?page=comments#action_12416664 ]


Kenneth Xu commented on COLLECTIONS-110:
----------------------------------------

I have been digging hard into mailing archive recently as well as spent sometime poking around
both collections@sf and collections15@sf (c@sf and c15@sf here after). I respect the amont
of hard work that has been put in to both projects. 

Let me start by the old post:
http://marc.theaimsgroup.com/?l=jakarta-commons-dev&m=111706676608332&w=2

And the entire thread:
http://marc.theaimsgroup.com/?t=111686614000003&r=1&w=2

IMHO, the backward compatibility of c@sf is great but unfortunately, a lot of classes are
not properly generified and violates one of important rule of generics, that is "you are type
safe unless you get a warning". One of the examples is the ChainedTransformer. c15@sf did
a much better job of generifying the ChainedTransformer but it changed the class entirely
and make it impossible to be backward compatible.

I'm thinking it would be nice if we can simply deprecate the ChainedTransformer untouched
and introduce a new generified TransformerChain like c15@sf did.

OK, I'm proposing a new approach here, generify those class that can be properly generified,
deprecate those methods/classes that cannot be generified and replaced it with new generic
version. Also deprecate duplicated methods/classes that JDK 1.5 provides, for example CollectionUtils.unmodifiableCollections.

The goal is to have a properly generified commons-collections that is fully backward compatible.
And if possible, hoping to replace the corrent code base with retroweaver to support 1.2 JVM.

Any thoughts?

> [collections] Support parametized classes with commons.collections.
> -------------------------------------------------------------------
>
>          Key: COLLECTIONS-110
>          URL: http://issues.apache.org/jira/browse/COLLECTIONS-110
>      Project: Commons Collections
>         Type: Bug

>  Environment: Operating System: other
> Platform: Other
>     Reporter: Colbert Philippe

>
> It's time to create a parallel version of commons.collections to support 
> parametized classes of each container class and abstract class.  It's not that 
> hard.  There is a 23 PDF document on Sun Java website describing in detail how 
> it should be done and what to watch out for.
> I already converted a few classes from commons.collection privately for my own 
> needs.  Once you get the hang of it, it's a rather quick process.
> I am even willing to volunteer my time to do some more but I need the 
> collaboration of some of the original programmers to watch over things.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message