Session Time Out issues after logging out

0
0

I am creating an application, and while testing it i noticed something odd. When I log out, using  Application.Exit();  – it takes me back to the login screen. But if i leave it there for a few minutes I get the standard “Session is about to expire” message with the count down. Has something changed in the latest WiseJ release ? I don’t think I am having this issue on an application I deployed last year.

 

So – does this mean the session is really still active when you do an  Application.Exit();?

General
Share
  • You must to post comments
Filter
Sort by: Recently Active
0
0

Application.Exit() removes the session immediately and informs the client that the session is terminated.

The client removes all objects from the page. Now you are left with only 2 options: 1) leave a blank page; 2) reload and let the application restart. We received several requests to reload since a blank screen is not optimal.

If you let the new session expire that you get the built-in user inactivity form. You can override the behavior and decide what to at every step. You can override the SessionTimeout event on the server, you can override the client behavior and load an html page, etc. If you load a new Wisej page or window than you get a new session.

Sessions are not related to your application’s login. Loggin in or not is an application’s behavior.

  • edmond girardi
    But since the application in the browser is now sitting at the login screen, and no session has started -why is it showing the timeout message ? I didn’t let the session expire – I logged out, and now it sits at the login screen as it should – however, it’s misleading to say the session will expire as no one has logged in yet.
  • Luca
    • Luca
    • Jun 4, 2018 - 1:01 pm
    Wisej doesn’t have a login screen. The login screen must be a window or a page from your app. If you leave the session for a while it will timeout. Logging in your application is not related to a web session. The web session is created immediately. Logging in or or not makes no difference to the session, it’s just a screen. You can handle the SessionTimeout event and show something else or prolong the session.
  • edmond girardi
    Got it – I thought that it worked more like VWG when application.exit was called it terminated the session. But I guess if it comes back to the same “login page” it starts the “WISEJ” session again
  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.