Eclipse Remote Application Platform 3.1.0 Release Review

End Date of the Review Period

Reviews run for a minimum of one week. The outcome of the review is decided on this date. This is the last day to make comments or ask questions about this review.




RAP 3.1 is a minor update in the 3.x release stream. It adds support for UIs with right-to-left orientation (as used in the Arabic world), and integrates an improved CKEditor from the RAP Incubator project. Additionally, the performance has been improved by extending the new on-demand change detection.

API Certification

The project leadership certifies that the APIs in this release are "Eclipse Quality".

Security Issues

No known security issues.

Non-Code Aspects

The RAP Developer's Guide has been updated; it is available as part of the RAP Tools and on the project web site.

Examples and demos are included in the examples feature, and have been tested with 3.1. Release versions of the examples are deployed online available at

Usability Details

No usability issues.

End of Life

No change compared to RAP 3.0.

  • RWT requires javax.servlet version 2.5 .. 3.1
  • OSGi integration compatible with OSGi core spec
  • RAP protocol uses strict JSON as specified in RFC 4627
  • Java compiler level and minimum execution environment is Java 7 (JavaSE-1.7), but Java 8 (JavaSE-1.8) is required JFace Databinding support
  • 4 active committers
  • Continuous committer activity
  • Increasing number of external contributors
  • Steady flow of bug reports in bugzilla (~ 10 bug reports / month, including feature requests)
  • Very active discussions on the community forum/newsgroup
  • Blogs with N&N information about RAP at, aggregated on Planet Eclipse
  • Integration with other Eclipse projects
    • Eclipse 4 support in the RAP Incubator
    • EMF provides RAP support
    • RAP is one of the target platforms of EMF Client Platform
    • RAP Tools is part of the EPP RCP/RAP package download
    • RAP Incubator provides RAP versions of many other components
  • Active role in the LTS working group


This release is part of Neon