RAP 2.0 M3 is available

The RAP team has been working hard over the last weeks and made another milestone build for RAP 2.0 available today.

RAP 2.0 M3 contains a brand new event system implementation that allowed us to get rid of some old bugs and to attach listeners more precisely in the protocol. Many RAP developers will like the new Client API that provides access to client features through a service locator interface. With this new interface, RAP finally offers a public API to execute JavaScript on the client, using the new JavaScriptExecutor service (check Ivan’s post for details):

JavaScriptExecutor executor = RWT.getClient().getService( JavaScriptExecutor.class );
if( executor != null ) {
  executor.execute( "alert( \"Hello World!\" );" );
}

Some public classes and interfaces, most notably the resource manager, have been cleaned up in M3 and made ready for RAP 2.0. After 6+ years of development, RAP’s API simply needs some cleanup. But don’t worry, we will keep the number of breaking changes low and let deprecated classes in place where possible to ease the migration. And we’re maintaining a RAP 2.0 migration guide to assist you.

For a more detailed list of changes and bugfixes in this milestone, have a look at our New and Noteworthy page. The build is available for download on the project’s download page and is also included in the Eclipse Kepler repository: https://download.eclipse.org/releases/kepler/.

RAP 2.0 is going to be released in February 8, 2013. For next year’s simultaneous release, Eclipse Kepler, we’ll plan a follow-up release. We hope you are as excited about RAP 2.0 as we are and the migration goes smooth for you. Let us know what you think!

1 Comment
  • Franco
    Posted at 02:21, 2013-01-17

    Good post.From the context menu, I would rtaher recommend the Add to Java Search’ functionality instead of the import functionality. This way you would be able to browse the code without having to import the entire universe into your workspace.The Add to Java Search’ is a hidden treasure. Hopefully, we can have it better integrated with JDT in 3.4.See