We have no plans to support reflection in client-side code. What problem
are you trying to solve?
http://gwt-code-reviews.appspot.com/1855803/
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
http://gwt-code-reviews.appspot.com/1855803/diff/1003/user/super/com/google/gwt/emul/java/lang/reflect/Type.java
File user/super/com/google/gwt/emul/java/lang/reflect/Type.java (right):
I'm not sure this is worth doing. It's not just a matter of approving
the change; the Class class is handled specially in GWT and it would
take me a while to prove that it's safe.
Also, this doesn't seem like a particularly good design practice to
support. Shared code should work on both client
If you really want to do this, I'd advocate just shadowing the class
put super-sourcing your own implementation of java.lang.Class.
Probably adding an empty method that always returns null is safe,
because it'll just be promoted to a global static function and inlined
as 'null', e.g.
