I believe type parameters work fine. Can you give an example that doesn't work? I just tried modifying EnumTest to verify that at least in simple cases, it works.
The way this works relies on Java generics having been defined to have compatibility with pre-generic Java. You can always erase a type and use that instead of the original, complex type--though of course losing the benefits of type checking. By using erased types, GWT's current implementation is a bit simpler. That's the theory. Do you have an example of something you'd like to work that does not? If so, we can patch it as you describe. However, one more thing that needs to be done is to handle bounds on the type parameters. For this facility to be useful in practice, the type parameters will need to be bounded anyway, because otherwise the RPC interface will effectively specify that objects must be passed back and forth. http://gwt-code-reviews.appspot.com/575801/show -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
