Skip to Content
avatar image
Former Member

User session access in WebDynpro

Dec 12, 2003 at 04:47 PM | 15 Views

Hi All,

Does anybody know how can I obtain access to the user's session? Normally in standard J2EE web applications there is an object "session" and one can bind sime attributes to it.

Regards,

Metodi

UI Web Dynpro Java
Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Dec 12, 2003 at 05:50 PM

    Hi Metodi,

    We also have such a mechanism, but we do not use the httpSession directly. There is a Wrapper called ClientSession that offers a Map with the same lifetime that a httpSession. The framework uses that mechanism to retrieve and store information.

    But that API not public as the usage is somehow "dangerous" and out of framework control when memory is limited. We would like to learn more about the use case so that we can offer some alternatives. If there is no other way and the use case requires it, the API can be used.

    Regards

    Karin

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member
      Dec 15, 2003 at 08:37 PM

      Hi Metodi,

      as fas as i know, your Web Dynpro application will be terminated gracefully, if the application is exited by session expiration and/or user logoff. This happens even if the user closes the browser window or pressing Alt+F4.

      The CSF sends a specific event to the server, which then handles the rest. The Web Dynpro runtime (indirectly) calls the wdDoExit method of the Component controller, which was the entry point of the active application and then top-down the controller hierarchy (i'm not really sure about the last point). So the wdDoExit methods of the specific controllers are the right place for you to do your clean up tasks.

      Wouldn't it be possible to bind the session specific information to the configuration context of a component for example? The ClientSession is not public, i guess, so there's no documentation.

      Regards

      Stefan