Yeah, I tried that sort of setup with the ArrayUtils.toMap() method and it was shot down (http://apache-commons.680414.n4.nabble.com/Re-svn-commit-r983137-commons-proper-lang-trunk-src-main-java-org-apache-commons-lang3-ArrayUtils-jaa-td2317854.html). Good luck with that. It wasn't worth my time to continue to argue about it anymore, so I reverted it.
On Sun, Sep 4, 2011 at 5:22 AM, Simone Tripodi <simonetrip...@apache.org> wrote: > Hi all guys, > I think that generics could help us on improving the Context class; > I'm not particularly happy having it extending Map - it is needed > anyway for backward compatibility - but it is clear that Context is a > place where storing/retrieving objects identified by a key. > I propose adding two helper methods > > /** @since 2.0 */ > <T> T retrieve( String key ); > > /** @since 2.0 */ > <T> void store( String key, T object ); > > that would help users avoid the redundant code of type cast/checking > when assignments are already known (it throws a ClassCastException if > types are not assignable). > At the same time, old pattern is supported, users can choose their > preferred way to go, depending on their needs. > WDYT? > Many thanks in advance, all the best! > Simo > > http://people.apache.org/~simonetripodi/ > http://www.99soft.org/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
