Exception is already Serializable and GWT accepts Serializable in lieu of
IsSerializable. If possible, it would be nice to keep GWT references out of narya-base (where com.threerings.web ends up). I'm already dealing with the breakage caused by GWT in narya-distrib, but I'd rather not have to filter GWT out of narya-base *and* narya-distrib in every Proguard configuration from here to Gomorrah, if possible. git-svn-id: svn+ssh://src.earth.threerings.net/narya/trunk@6187 542714f4-19e9-0310-aa3c-eee0fc999fb1
This commit is contained in:
@@ -3,14 +3,11 @@
|
||||
|
||||
package com.threerings.web.gwt;
|
||||
|
||||
import com.google.gwt.user.client.rpc.IsSerializable;
|
||||
|
||||
/**
|
||||
* An exception thrown by a remote service when it wishes to communicate a
|
||||
* particular error message to a user.
|
||||
*/
|
||||
public class ServiceException extends Exception
|
||||
implements IsSerializable
|
||||
{
|
||||
/**
|
||||
* Creates a service exception with the supplied translation message.
|
||||
|
||||
Reference in New Issue
Block a user