The RAP Tooling has Offspring

Home  >>  Eclipse  >>  The RAP Tooling has Offspring

The RAP Tooling has Offspring

On October 28, 2011, Posted by , In Eclipse, By , , With Comments Off on The RAP Tooling has Offspring

I would like to use the opportunity to point you to a feature of RAP that is around for some time now but has gone almost unnoticed so far.

The RAP tooling has grown by yet another launch configuration. With the RWT Application Launcher you can run RWT applications with just one shortcut.

If you haven’t heard of RWT yet, think of it as SWT/Web. RWT is RAP without the workbench and OSGi, it plays the same role in RAP as SWT does for the Eclipse Platform/RCP. RWT lets you develop lightweight, modular, and dynamic web applications.

The short movie shows how easy it is to launch your RWT code.

From the package explorer, or from the Java editor, or any selection that points to an IEntryPoint you can choose Run As > RWT Application (or Alt+Shift+X 3 if you prefer). This command creates and runs an RWT launch configuration for the selected entry point. It starts a servlet engine, “deploys” the selected entry point, and opens a browser window with the application running therein.

As with all Eclipse launchers, the generated launch configuration can be edited and details such as the server port, the servlet path and if an internal, external or no browsers should be opened may be altered. Of course you are free to create a launch configuration from scratch if you prefer.

Apart from launching RWT applications you can also run an arbitrary web application. In the RWT launch configuration dialog you can choose a web.xml and specify the servlet path to be opened in the browser (if any).

See also  Clean Sheet Service Update (0.8)

The RWT application launcher is available since RAP 1.4. If you would like to try out this feature you can get it from the RAP downloads page. Please let us know what you think. If you are missing feature or if you find a bug, please open a bug report.

Rüdiger Herrmann
Follow me
Latest posts by Rüdiger Herrmann (see all)
Comments are closed.