I'm making a login application, and I need to make an RPC call to
authenticate the user. The way things are set up is that there's
already a server with a deployed GWT servlet running, and the client
code that I am running will not be run from a page server by that
server. The "page" that makes the request is actually just JS in a FF
extension. So it's not really a traditional RPC call in the sense that
the client and server sides are on different hosts completely.
The call itself is quite simple - the client passes to the server 3
Strings containing various authentication information, and the server
responds with a String. However, when I do make the call, it executes
fine, but the onFailure function of the callback is called with the
following exception:
[INFO]
com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException:
This application is out of date, please click the refresh button on
your browser
I've asked around about this, but no one has been able to provide me
with a solution. I've been suggested to re-deploy the servlet on the
remote server, but seeing as how it's remote, I'd really like to avoid
doing that unless I was absolutely sure that would solve the problem.
Other suggestions of things to try would be greatly appreciated.
I was running GWT 1.4.61, but tried it on 1.4.62 and it's the same
thing.
If it's helpful to diagnose, I can post the relevant code as well.
> I'm making a login application, and I need to make an RPC call to
> authenticate the user. The way things are set up is that there's
> already a server with a deployed GWT servlet running, and the client
> code that I am running will not be run from a page server by that
> server. The "page" that makes the request is actually just JS in a FF
> extension. So it's not really a traditional RPC call in the sense that
> the client and server sides are on different hosts completely.
> The call itself is quite simple - the client passes to the server 3
> Strings containing various authentication information, and the server
> responds with a String. However, when I do make the call, it executes
> fine, but the onFailure function of the callback is called with the
> following exception:
> [INFO]
> com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException:
> This application is out of date, please click the refresh button on
> your browser
> I've asked around about this, but no one has been able to provide me
> with a solution. I've been suggested to re-deploy the servlet on the
> remote server, but seeing as how it's remote, I'd really like to avoid
> doing that unless I was absolutely sure that would solve the problem.
> Other suggestions of things to try would be greatly appreciated.
> I was running GWT 1.4.61, but tried it on 1.4.62 and it's the same
> thing.
> If it's helpful to diagnose, I can post the relevant code as well.
> I'm making a login application, and I need to make an RPC call to
> authenticate the user. The way things are set up is that there's
> already a server with a deployed GWT servlet running, and the client
> code that I am running will not be run from a page server by that
> server. The "page" that makes the request is actually just JS in a FF
> extension. So it's not really a traditional RPC call in the sense that
> the client and server sides are on different hosts completely.
> The call itself is quite simple - the client passes to the server 3
> Strings containing various authentication information, and the server
> responds with a String. However, when I do make the call, it executes
> fine, but the onFailure function of the callback is called with the
> following exception:
> [INFO]
> com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException:
> This application is out of date, please click the refresh button on
> your browser
> I've asked around about this, but no one has been able to provide me
> with a solution. I've been suggested to re-deploy the servlet on the
> remote server, but seeing as how it's remote, I'd really like to avoid
> doing that unless I was absolutely sure that would solve the problem.
> Other suggestions of things to try would be greatly appreciated.
> I was running GWT 1.4.61, but tried it on 1.4.62 and it's the same
> thing.
> If it's helpful to diagnose, I can post the relevant code as well.
Nevermind, the debugging error is simply because the debugger doesn’t
have the sources to step through, because it’s trying to debug the
remote server code. So it doesn’t look there’s anyway to fix that
unless I can add the remote server code as the source, which I don’t
think you can do with a deployed servlet.
On May 29, 4:43 pm, Dmitri V <dmitri...@gmail.com> wrote:
> Weirdly enough, when I debug the application instead of running it, I
> get this error in Eclipse:
> source not found.
> NativeMethodAccessorImpl.invoke(Object, Object[]) line: not available
> DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: not
> available
> Method.invoke(Object, Object…) line: not available
> IDispatchImpl.callMethod(CompilingClassLoader, Object, Variant[],
> Method) line: 126
> MethodDispatch.invoke(int, int, Variant[]) line: 88
> MethodDispatch(IDispatchImpl).Invoke(int, int, int, int, int, int,
> int, int) line: 293
> MethodDispatch(IDispatchImpl).method6(int[]) line: 196
> COMObject.callback6(int[]) line: 117
> OS.DispatchMessageW(MSG) line: not available [native method]
> OS.DispatchMessage(MSG) line: 1925
> Display.readAndDispatch() line: 2966
> GWTShell.pumpEventLoop() line: 689
> GWTShell.run() line: 550
> GWTShell.main(String[]) line: 321
> Can someone shed some light on what this is saying?
> On May 28, 1:47 pm, Dmitri V <dmitri...@gmail.com> wrote:
> > Hi,
> > I'm making a login application, and I need to make an RPC call to
> > authenticate the user. The way things are set up is that there's
> > already a server with a deployed GWT servlet running, and the client
> > code that I am running will not be run from a page server by that
> > server. The "page" that makes the request is actually just JS in a FF
> > extension. So it's not really a traditional RPC call in the sense that
> > the client and server sides are on different hosts completely.
> > The call itself is quite simple - the client passes to the server 3
> > Strings containing various authentication information, and the server
> > responds with a String. However, when I do make the call, it executes
> > fine, but the onFailure function of the callback is called with the
> > following exception:
> > [INFO]
> > com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException:
> > This application is out of date, please click the refresh button on
> > your browser
> > I've asked around about this, but no one has been able to provide me
> > with a solution. I've been suggested to re-deploy the servlet on the
> > remote server, but seeing as how it's remote, I'd really like to avoid
> > doing that unless I was absolutely sure that would solve the problem.
> > Other suggestions of things to try would be greatly appreciated.
> > I was running GWT 1.4.61, but tried it on 1.4.62 and it's the same
> > thing.
> > If it's helpful to diagnose, I can post the relevant code as well.
If I'm reading this correctly, you're trying to call from one domain
to another? Sounds like a cross-domain security issue, where the
browsers don't allow you to call from one server to another outside
it's domain.
On May 29, 5:19 pm, Dmitri V <dmitri...@gmail.com> wrote:
> Nevermind, the debugging error is simply because the debugger doesn’t
> have the sources to step through, because it’s trying to debug the
> remote server code. So it doesn’t look there’s anyway to fix that
> unless I can add the remote server code as the source, which I don’t
> think you can do with a deployed servlet.
> On May 29, 4:43 pm, Dmitri V <dmitri...@gmail.com> wrote:
> > Weirdly enough, when I debug the application instead of running it, I
> > get this error in Eclipse:
> > Can someone shed some light on what this is saying?
> > On May 28, 1:47 pm, Dmitri V <dmitri...@gmail.com> wrote:
> > > Hi,
> > > I'mmakinga login application, and I need to make anRPCcallto
> > > authenticate the user. The way things are set up is that there's
> > > already a server with a deployed GWT servlet running, and the client
> > > code that I am running will not be run from a page server by that
> > > server. The "page" that makes the request is actually just JS in a FF
> > > extension. So it's not really a traditionalRPCcallin the sense that
> > > the client and server sides are on different hosts completely.
> > > Thecallitself is quite simple - the client passes to the server 3
> > > Strings containing various authentication information, and the server
> > > responds with a String. However, when I do make thecall, it executes
> > > fine, but the onFailure function of the callback is called with the
> > > following exception:
> > > [INFO]
> > > com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException:
> > > This application is out of date, please click the refresh button on
> > > your browser
> > > I've asked around about this, but no one has been able to provide me
> > > with a solution. I've been suggested to re-deploy the servlet on the
> > > remote server, but seeing as how it's remote, I'd really like to avoid
> > > doing that unless I was absolutely sure that would solve the problem.
> > > Other suggestions of things to try would be greatly appreciated.
> > > I was running GWT 1.4.61, but tried it on 1.4.62 and it's the same
> > > thing.
> > > If it's helpful to diagnose, I can post the relevant code as well.
> If I'm reading this correctly, you're trying to call from one domain
> to another? Sounds like a cross-domain security issue, where the
> browsers don't allow you to call from one server to another outside
> it's domain.
> On May 29, 5:19 pm, Dmitri V <dmitri...@gmail.com> wrote:
> > Nevermind, the debugging error is simply because the debugger doesn’t
> > have the sources to step through, because it’s trying to debug the
> > remote server code. So it doesn’t look there’s anyway to fix that
> > unless I can add the remote server code as the source, which I don’t
> > think you can do with a deployed servlet.
> > On May 29, 4:43 pm, Dmitri V <dmitri...@gmail.com> wrote:
> > > Weirdly enough, when I debug the application instead of running it, I
> > > get this error in Eclipse:
> > > Can someone shed some light on what this is saying?
> > > On May 28, 1:47 pm, Dmitri V <dmitri...@gmail.com> wrote:
> > > > Hi,
> > > > I'mmakinga login application, and I need to make anRPCcallto
> > > > authenticate the user. The way things are set up is that there's
> > > > already a server with a deployed GWT servlet running, and the client
> > > > code that I am running will not be run from a page server by that
> > > > server. The "page" that makes the request is actually just JS in a FF
> > > > extension. So it's not really a traditionalRPCcallin the sense that
> > > > the client and server sides are on different hosts completely.
> > > > Thecallitself is quite simple - the client passes to the server 3
> > > > Strings containing various authentication information, and the server
> > > > responds with a String. However, when I do make thecall, it executes
> > > > fine, but the onFailure function of the callback is called with the
> > > > following exception:
> > > > [INFO]
> > > > com.google.gwt.user.client.rpc.IncompatibleRemoteServiceException:
> > > > This application is out of date, please click the refresh button on
> > > > your browser
> > > > I've asked around about this, but no one has been able to provide me
> > > > with a solution. I've been suggested to re-deploy the servlet on the
> > > > remote server, but seeing as how it's remote, I'd really like to avoid
> > > > doing that unless I was absolutely sure that would solve the problem.
> > > > Other suggestions of things to try would be greatly appreciated.
> > > > I was running GWT 1.4.61, but tried it on 1.4.62 and it's the same
> > > > thing.
> > > > If it's helpful to diagnose, I can post the relevant code as well.
