yes thats the exception. But still <T> is not really a substitute for the Class object Because if you just ignore generics then you can do what ever you want and currently you will get an exception..
But i guess it cleans up the api so that will be a break if nobody objects., johan On 10/22/07, John Patterson <[EMAIL PROTECTED]> wrote: > > > On 22 Oct 2007, at 15:16, Philip A. Chapman wrote > > I've always thought of adding generics as an api change. Sure, > > it's one > > that doesn't break backward compatibility, but it's a change non the > > MetaDataKey(Class) -> MetaDataKey<T> > > would count as an API change? Because the keys are always subclassed > the type information is available at run-time no? >
