GWT RPC servlet doesn't get called

[Yaakov]

Hi,

I have an GWT RPC call set up that has been working for a while. I
don't know what I changed (certainly nothing in the service nor async
interfaces), but now I can see in the debugger that I make the async
call, but looking in Firebug the request to the server never gets
made.

Does anyone have any idea of what it could be?

I already cleared the gwt-generated directory in the war directory and
still nothing... What could it be???

Thanks,
Yaakov.

[Yozons Support on Gmail]

What does the console show?  You should see a POST to your service name.  Make sure the POST URL matches how your web.xml is set up to process the requests.

[Yaakov]

I am not running with Jetty (i.e., running with no-server checked
off)... deployed to Glassfish.

However, I AM looking in Firebug and the call to the server NEVER gets
made!

In fact, I run it in debug mode and see the following:
***********************
It goes into an object caled VMTreeViewService_Proxy
(VMTreeViewService is the name of the main interface, i.e., not the
async one).

Then, it goes into
com.google.gwt.user.client.rpc.impl.RemoteServiceProxy

Then, back to VMTreeViewService_Proxy.

Then, it goes to JavaScriptHost.java (line 35):
return sHost.invokeNativeBoolean(name, jthis, types, args);

Then, to ModuleSpace (line 146).....

Then, eventually, it gets back to VMTreeViewService_Proxy. Inspecting
that object, btw, I do see the property remoteServiceURL as the URL
that should get called. the problem is that I never see it get called
(neither in Firebug nor in the server console).
***********************

I am also looking at my Eclipse console, at the Hosted mode console,
and at the server console. There are NO errors at all in either!

Any idea what could be going on here? I didn't change ANY code that
has to do with client side interfaces.

Thank you,
Yaakov.

[Yaakov]

Ok, never mind... It was a regular GWT SerializationException which
was getting swallowed up by ext-GWT widget code.

Thanks,
Yaakov.