o GWT RPC transfer object must be serialized
o All service method parameters and return type must be serializable
o Object implement the Serializable or IsSerializable interface, directly
or indirect. GWT serialization is not complete for all Java Serializable types.
o We don’t have data objects to be serialized so we will
not use this feature in our simple project.
o All service method parameters and return type must be serializable
o Object implement the Serializable or IsSerializable interface, directly
or indirect. GWT serialization is not complete for all Java Serializable types.
o We don’t have data objects to be serialized so we will
not use this feature in our simple project.
o GWT exceptions can be in two category: Unexpected (Unchecked) and Checked exceptions
Unexpected are really the runtime exceptions that can occur when network,
server, or hard drive has crashed is not working properly. RuntimeException
can also generate unexcepted exception like a NullPointerException.
Unexpected are really the runtime exceptions that can occur when network,
server, or hard drive has crashed is not working properly. RuntimeException
can also generate unexcepted exception like a NullPointerException.
Checked exception are the throwable expeptions handled by the code and
we want the client-side code to be able to handle it.
o GWT handle Unexpected and Checked exceptions differently
When checked exceptions occur, GWT will serialize the exception and
send it back to the client side.
Unexpected exception are sent to the development mode log, where you
can find the full stack trace. For these type of method, the generic
InvocationException will be thrown with “The call failed on the server”
message.
o Remember the IllegalArgumentException, if we drill to what
package it inherits, we see that it is a java.lang.RuntimeException.
o That’s an unchecked exception, hence unexpected types