UIThreads / EntryPoints [message #1827853] |
Mon, 25 May 2020 13:11  |
Eclipse User |
|
|
|
Hello
We are developping a new version of our app, this time without workbench or OSGI.
Just a "basic" RWT stand-alone in JEE_COMPATIBILITY. mode.
We face troubles with the use of entry points.
We would like to keep the created UI objects, such as the main shell and menus for instance.
Going from an entry point to another makes the server create a new UISession.
That way, created objects can no longer be accessed (not the thread that created the shell/widgets).
After several days of searching, we could not find a way to do so.
Sorry for that beginner question...
Is it possible to keep the UISession (with the help of cookies ?) or is there a better way to achieve this ?
Thank you for your help
|
|
|
|
|
Re: UIThreads / EntryPoints [message #1828843 is a reply to message #1828790] |
Fri, 19 June 2020 14:16  |
Eclipse User |
|
|
|
Hello
using the entry points to define sub-sets in our web app (e.g. /login, /admin, /main, ...),
it would be nice if we could keep alive the created objects like side menus, banners, views and editors (our own, not from the workbench) like we do with non-UI objects throughout the entire app.
Say the main shell contains widgets like a navigation pane or a widget allowing to go to and to go back from another part of the web app, or some editors with an ongoing action.
What can we do to keep this shell and its elements (composite, custom widgets, ...) ?
Since the UI thread is different at each entry point, accessing the shell triggers an exception (not the right thread).
So we need to re-create those objects each time the user gets to another entry point.
We do use the HTTP session to store our user session after the login.
But nothing else UI related.
Maybe we misunderstood the RAP documentation and RAP without workbench/OSGI is meant to be used this way: 1 URL entry point = 1 app.
We thought UI objects could be retrieved using:
RWT.getUISession(Display)
Thank you for your help.
|
|
|
Powered by
FUDForum. Page generated in 0.06457 seconds