Thanks, Colin. I'll double-check my module file and make sure the
exceptions are being included for the GWT compiler. That may be the
reason they're being missed.
On Sep 1, 2:14 pm, Colin Alworth niloc...@gmail.com wrote:
On Thursday, August 25, 2011 3:09:22 PM UTC-5, Ryan wrote:
However, if
On Thursday, August 25, 2011 3:09:22 PM UTC-5, Ryan wrote:
However, if I declare AException in the client, but throw either of
the two child classes in the server, GWT wraps it in an
InvocationException.
This is the key to your issue - if the client can't de-serialize it (because
the
On Aug 26, 12:51 am, Paul Robinson ukcue...@gmail.com wrote:
You shouldn't need to do anything. It should work as you thought. That is,
you can throw any subclass of the declared exception(s).
Is there something about BException and CException that stops them from being
gwt-serializable?
You shouldn't need to do anything. It should work as you thought. That is, you
can throw any subclass of the declared exception(s).
Is there something about BException and CException that stops them from being
gwt-serializable?
Alternatively, maybe it's because AException extends
My understanding is that in GWT-RPC, if a service throws an exception
declared in the signature, then GWT will report that exception back to
the client as-is. If it's any other exception that's thrown, then GWT
wraps it in an InvocationException.
I have a hierarchy of exceptions that could get
Can anyone atleast let me know if what i am looking at is feasible in
first place.
Thank you!
On Nov 14, 3:16 pm, keyboard_samurai yog...@gmail.com wrote:
Hi,
I am curious to find out if we can override few features in GWT to
achieve the following :- In GWT if we want an exception to be
Hi,
I am curious to find out if we can override few features in GWT to
achieve the following :- In GWT if we want an exception to be
propagated to the client, the interfaces (extending RemoteService)
should have the throws explicitly declared. In our project we have an
exception hierarchy defined
Hi, I have tried the following:
public class UserNotFoundException extends Exception implements
Serializable {
// serial uid
private static final long serialVersionUID = 1L;
public UserNotFoundException(String msg) { super(msg); }
}
...and then in my service interface:
To be gwt-serializable, you must have a no-arg constructor
davis wrote:
Hi, I have tried the following:
public class UserNotFoundException extends Exception implements
Serializable {
// serial uid
private static final long serialVersionUID = 1L;
public
Thanks Paul -- just figured that out. Would be a great time-saver if
it told me that explicitly :)
On Aug 4, 10:22 am, Paul Robinson ukcue...@gmail.com wrote:
To be gwt-serializable, you must have a no-arg constructor
davis wrote:
Hi, I have tried the following:
public class
Methods defined in the Async interface should not throw exceptions
(otherwise you have to surround them by a try catch bloc when using it
in your client code) and must have void return types :
public void getName(int id,AyncCallback);
instead of
public String getName(int id,AyncCallback) throws
Hi All,
I am having a problem in getting exception messages from exception in
onFailure method.
My services are like
//Client Side
public String getName(int id) throws ClientException;
public String getName(int id,AyncCallback) throws ClientException;
//Server Side
public String getName(int
12 matches
Mail list logo
