Bug 460313 - [e4 on RAP] Let e4 run with JEE compatible operation mode
Summary: [e4 on RAP] Let e4 run with JEE compatible operation mode
Status: NEW
Alias: None
Product: RAP
Classification: RT
Component: Incubator (show other bugs)
Version: unspecified   Edit
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-19 04:31 EST by Peter Kullmann CLA
Modified: 2015-08-27 08:58 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Kullmann CLA 2015-02-19 04:31:01 EST 
(This comes from a forum discussion: https://www.eclipse.org/forums/index.php?t=rview&goto=1622904#msg_1622904)

RAP can be run in two modes: The classical SWT threading model or the JEE compatible operation mode which allows RAP to run on a high-availability cluster (see https://wiki.eclipse.org/RAP/RWT_Cluster).

When running the 3.x Workbench on RAP we only have the classical SWT model which does not allow persistent sessions.

It would be great if e4 on RAP could run in the JEE mode.

Tom said: "We still need to rely on display spinning so we need to run in compat mode.

If you file a bug we could try looking into this and maybe find a solution but I can't guarantee."
Comment 1 Thomas Schindl CLA 2015-08-27 08:58:11 EDT 
A major problem to run with out event loop spinning are blocking e4  APIs eg in EPartService like:
* savePart
* saveAll

We's first have to convince the upstream devs that they should introduce methods with callbacks or Futures replacing the original ones.