> a custom class that extends Exception That must be it; we have a couple of custom classes that just extend Exception:
./InitializationException.java:public class InitializationException extends Exception ./RPCException.java:public class RPCException extends Exception Would we be better off using one of the Exception types that GWT emulates? Or is this just an annoying-but-harmless warning? On Dec 10, 2:31 am, Gabor <[email protected]> wrote: > If your method throws Exception, or a custom class that extends > Exception, then you will get this warning. Maybe because the GWT > compiler searches for all subclasses of Exception, and finds > SerializableException. It includes it in the list of serializable > types, and you get a deprecation warning. I don't know how to make it > go away, without going back to 1.7. > > On Dec 10, 12:13 am, rjcarr <[email protected]> wrote: > > > > > I'm attempting to upgrade to GWT 2.0 and everything is working well > > enough except I am getting this warning in the compile step: > > > Referencing deprecated class > > 'com.google.gwt.user.client.rpc.SerializableException' > > > And the file it mentions is a gwt derived file with the suffix: > > _TypeSerializer.java > > > The warning always happens on service classes (i.e., RemoteService), > > but doesn't seem to happen on *all* service classes. > > > I have not defined SerializableException explicitly, but my method > > signatures do throw Exception. > > > Any idea why this is happening and what I can do to make it go away? > > > Thanks! -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
