Bug 365640 - [Tooling] RWT launcher fails with SWT snippets
Summary: [Tooling] RWT launcher fails with SWT snippets
Status: ASSIGNED
Alias: None
Product: RAP
Classification: RT
Component: Demo (show other bugs)
Version: 1.5   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-05 12:44 EST by Ralf Sternberg CLA
Modified: 2011-12-05 15:45 EST (History)
0 users

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 Ralf Sternberg CLA 2011-12-05 12:44:35 EST 
Since JEE_COMPATIBILITY is now the default mode, the RWT Launcher fails when a main loop is present in the started entrypoint. With this change it is no longer possible to launch ordinary SWT snippets.

It would be nice if the RWT launcher would continue to launch snippets with a main loop by setting the operation mode to SWT_COMPATIBILITY, either manually or, if possible, even under the hood.
Comment 1 Rüdiger Herrmann CLA 2011-12-05 15:45:50 EST 
The launcher currently creates a web.xml file on the fly which uses the (undocumented) org.eclipse.rwt.entryPoints init-param to specify the entry point to be run.
We could change RWT in that is sets the operation mode to SWT_COMPATIBILITY when this init-param is specified. See EntryPointRunnerConfigurator.