Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 6.1.6
-
Fix Version/s: 6.2.0pre0
-
Component/s: Continuations
-
Labels:None
-
Environment:Windows XP
-
Number of attachments :
Description
From the original JETTY-399 issue raised by Craig Day ...
------------------
The OpenRemoteServiceServlet provided doesn't work with GWT 1.4. They seem to have changed RemoteServiceServlet significantly in this release, and although RemoteServiceServlet has been "opened up" more I couldn't get around not creating a 1.4 compatible version of OpenRemoteServiceServlet. Let me know if you want me to submit the code,.. largely trivial
Craig
------------------
GWT 1.4.60 in the deployed mode (i.e. war with a trivial Chat Room app deployed to Jetty webapps. IDE: Eclipse with WTP adapter for Jetty)
The GWT chat room app works as expected in the hosted mode since the Continuation instance being used is of type WaitingContinuation. When the app is deployed to the Jetty webapps directory and loaded in the browser, the Continuation instance created is of type RetryContinuation.
On calling "suspend" on the Continuation instance, the Throwable instance thrown is of type org.mortbay.jetty.RetryRequest. However, by the time the Throwable instance reaches the AsyncRemoteServiceServlet.doUnexpectedFailure method, its been replaced (by the GWT RPC class) by a SerializationException.
The detailedMessage in the exception reads
"Type 'org.mortbay.jetty.RetryRequest' was not assignable to 'com.google.gwt.user.client.rpc.IsSerializable' and did not have a custom field serializer. For security purposes, this type will not be serialized."
The protected method, "throwIfRetyRequest" in AsyncRemoteServiceServlet (Craig Day implementation) then fails to rethrow the original RetryRequest exception. As a result, the servlet container doesn't get the RetryRequest exception and the call to suspend fails.
Suggest modifying the implementation of the "throwIfRetyRequest" method to the following (unless there's a better way):
public class AsyncRemoteServiceServlet extends OpenRemoteServiceServlet
{
.....
private static final String JETTY_GWT_SERIALIZATION_EXCEPTION_MESSAGE = "Type 'org.mortbay.jetty.RetryRequest' was not assignable to 'com.google.gwt.user.client.rpc.IsSerializable'";
....
protected void throwIfRetyRequest(Throwable caught)
{
if (caught instanceof UnexpectedException)
String detailMessage = caught.getMessage();
if (caught instanceof SerializationException
&& detailMessage.startsWith(JETTY_GWT_SERIALIZATION_EXCEPTION_MESSAGE))
{
try
catch (ClassNotFoundException ex)
{
ex.printStackTrace();
}
catch (InstantiationException ex)
{ ex.printStackTrace(); } }
catch (IllegalAccessException ex)
throw (RuntimeException) caught;
}
if (caught instanceof RuntimeException
&& JETTY_RETRY_REQUEST_EXCEPTION.equals(caught.getClass()
.getName()))
}
....
}
Attachments
Issue Links
| This issue relates to: | ||||
| JETTY-399 | OpenRemoteServiceServlet not compatible with GWT 1.4 |
|
|
|
Jan, as our new GWT expert (
, can you put this update on your list of todos.
I'll help out with it - so ping me when you have a few hours spare to work on this.