Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 365640

Summary:	[Tooling] RWT launcher fails with SWT snippets
Product:	[RT] RAP	Reporter:	Ralf Sternberg <rsternberg>
Component:	Demo	Assignee:	Project Inbox <rap-inbox>
Status:	ASSIGNED ---	QA Contact:
Severity:	normal
Priority:	P3
Version:	1.5
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Ralf Sternberg

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

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.