@Thomas Broyer
Thanks and you are correct, after configuring the web services with CORS it
works like a charm. I added this filter to web.xml, carefully limiting CORS
to GET methods only.
CorsFilter
org.apache.catalina.filters.CorsFilter
cors.allowed.origins
A status code of 0 is generally indicative of a cross origin request without
CORS (or an aborted request or network error)
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an em
Did some additional investigation on this by trapping the Response object
in an exit filter and examining it. I found that the Response from Web
service is way different from the GWT-Server side code. Given below are the
screen-clips from both. Long story short - trapping the Jersey Web Service
Haven't used RestyGWT, but after reading thru different available options,
I recently switched to Errai JAX-RS, the setup is pretty straight forward
and it provides out of the box jackson serialization/de-serialization and
cross-domain access.
On Tuesday, November 8, 2016 at 4:10:26 PM UTC-5,
@Thomas Broyer
Thanks for the prompt response and suggestions. I did switch to
GWT RequestCallback but the problem seems to larger than I expected.
It appears the GWT Response class and the Jersey Response classes may not
be compatible.
@GET
@Produces(MediaType.APPLICATION_JSON)
@Pa
JsonpRequestBuilder has a default timeout of 10 seconds, whereas
RequestBuilder doesn't have a timeout by default.
http://www.gwtproject.org/javadoc/latest/com/google/gwt/jsonp/client/JsonpRequestBuilder.html#setTimeout(int)
Anyway, if you can setup CORS on your server (Access-Control-Allow-Origin
Trying to retrieve an object in my GWT client using JsonpRequestBuilder
from a cross domain server. The call goes to server and server does
respond with the correct value but the client keeps throwing "Timeout while
calling http://localhost:8080/layouts/AVhARgXQW9-o1U_GgvJa"; message. Here
are
