[Isomorphic]

@andrewjohnson It's not typical to be bypassing SmartClient's comm layer *unless* you're using GWT-RPC - is that the problem?

You should normally see various requests in the RPC tab in the Developer Console.

[andrewjohnson]

Interesting I do see "some" of the requests in the developer console, but not all of them. Perhaps I need to look into the configuration further. Although for those that I do see they have the following properties:

Type: RPCRequest
Transport: xmlHTTPRequest

Assuming that's what we should see for all request?

thanks again.

[Isomorphic]

We keep asking: are you using GWT-RPC? If so, that's the problem (at least for those requests) because at that point SmartClient isn't involved in the HTTP layer at all.

It doesn't sound like you built that part of the application you're trying to modify - it makes sense to speak to the person who did, or look at the relevant code, rather than discuss the application as a 'black box' here.

[saforaziz]

ReLogin Server setup

We are considering putting in the ReLogin. What needs to be installed on the server side to get ReLogin to work? SmartGWT EE?

[Isomorphic]

No server-side components are required. Just ensure that when the session times out, the HTTP response sent by your server includes the loginRequiredMarker.

Oh and don't use GWT-RPC.

[alius]

No server-side components are required. Just ensure that when the session times out, the HTTP response sent by your server includes the loginRequiredMarker.

Oh and don't use GWT-RPC.

You can use GWT-RPC - only thing is : you will have to check for session time out in every server side RPC implementation and request re-login upon receiving error from server.

Maybe Isomorphic can provide some basic guidelines for GWT-RPC users to be in line with SmartClient structure?

Alius.

[Isomorphic]

Alius have you actually tried that out? The code that detects the loginRequiredMarker is in the RPCManager, which never gets involved when using GWT-RPC with the GWTRPCDataSource.

[alius]

I did not mean RPCManager.

Here is my general steps:
1.GWT-RPC call (from client)
2. In server side implementation first thing is: getThreadLocalRequest ().getSession (false)
3. Exception is thrown if there is no session.
4. (Client side) onFailure test for this exception type
5. Open login url with Window.open (GWT.getHostPageBaseURL () + "relative_login_url", "_self", null);

It works.

Step 5 can be replaced with popup login window.

Maybe you can provide some guidelines to make this approach cleaner?

Alius.

[Isomorphic]

@alius That achieves logging back in - by Relogin we mean specifically the feature of transparently re-sending the transaction that encountered a session timeout, without any loss of context, and without having to put error handling code in various UI components or DataSources. See RPCManager.suspendTransaction(), RPCManager.resendTransaction() and the Relogin overview.