Thanks for your quick answers!
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/HpFcB_Avyn0J.
To post to this group, send email to google-web-to
1. this only applies to gwt-rpc. for pure client code, everything is
completely known at compile time, so the compiler knows which
implementation is possibly going to be used.
2. you can use gwt's configurable blacklist/whitelist to prevent it from
making every possible subclass serializable and st
As I understand that only applies to gwt-rpc
On Saturday, November 24, 2012, shippi wrote:
> Hi!
>
> I am aware of the fact that the GWT best practices are slightly different
> from the regular java recommendations. There is one question i would like
> to clarify. I am
> aware of the fact that
Hi!
I am aware of the fact that the GWT best practices are slightly different
from the regular java recommendations. There is one question i would like
to clarify. I am aware of the fact that when writing RPCs than the best
practice is to use implementations as a return value f.e. ArrayList in
