|
|
|
| Re: UIThreads / EntryPoints [message #1828843 is a reply to message #1828790] |
Fri, 19 June 2020 18:16  |
 Thibaut Lafontaine
Messages: 4
Registered: July 2019
Location: Belgium |
Junior Member |
|
|
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.03170 seconds
] 
Search
Help
Register
Login
Home
