Celebrating Two Decades of Eclipse RAP: A Journey of Java, Innovation, and Community

June 21, 2026 marks exactly 20 years since the Eclipse Remote Application Platform (RAP) passed its creation review at the Eclipse Foundation. Two decades later, RAP is still here — still shipping, still evolving, still powering enterprise applications around the world.

For two decades, RAP has empowered developers to build powerful, modular business applications for the desktop, browser, and mobile using a single Java codebase. It is a project with a rich history — and today, we want to take a moment to celebrate not just the technology, but the people and the community that made it endure.

A Personal Perspective

I’m Markus, and my own story is deeply intertwined with RAP. Its predecessor, W4T, was one of the key reasons I joined Innoopract — the company behind EclipseSource. I was drawn to Innoopract by two things: their genuine commitment to Eclipse and the open source world, which had always been close to my heart, and the potential I saw in W4T — a cool Java web framework that was evolving into something much more ambitious: making the Eclipse development model work on the web. Over the years, I’ve worked as a consultant on large-scale RAP applications, was elected committer on the project in 2012, became co-project lead alongside Ralf Sternberg in 2013, and have continued in that role ever since — with Ivan Furnadjiev joining me as co-lead in 2016.

This journey is personal — and it’s far from over.

Part 1: The Genesis – “SWT for the Web”

The roots of RAP go back further than 2006. The story really begins in 2001, when Innoopract developed the W4T — the World Wide Web Windowing Toolkit — a bold attempt to shield Java developers from the complexities of HTML, CSS, and JavaScript, years before Google launched GWT with the same idea. Innoopract donated that codebase to the Eclipse Foundation, and the Rich Ajax Platform project passed its creation review on June 21, 2006 — the date we celebrate today.

The core idea was revolutionary for its time. Instead of wrestling with web technologies, developers could write their application logic in Java and use familiar APIs like SWT and JFace. The project’s early tagline said it all: “SWT for the Web.”

The RAP project homepage in 2006, shortly after the creation review — still in validation phase, with the original "Rich Ajax Platform" name and the iconic UFO mascot.

The first release, RAP 1.0, followed in October 2007 — the source code and its full history are available at github.com/eclipse-rap/org.eclipse.rap. From the very first release, Jochen Krause led the project. The W4T codebase itself was developed at Innoopract by Frank Appel and the team who had spent years solving the hard problems of server-side Java UI before the project was donated to Eclipse. Even before the creation review, the community had noticed: RAP won 4th prize at the JAX Innovation Award in May 2006, chosen from 48 submitted projects.

The JAX Innovation Award 2006, 4th prize — awarded to the Rich Ajax Platform in May 2006, weeks before the formal creation review at the Eclipse Foundation.

“Congratulations to Eclipse RAP on its 20th anniversary!

Looking back, my years with RAP from 2005 to 2008 were a very special time. I had the privilege of being team lead and technical lead during a phase where RAP was both a serious engineering effort and an incredible playground for solving hard problems. Bringing the Eclipse workbench model to the web came with plenty of technical challenges, but we had a great team, a strong sense of quality, and the ambition to build something that would last.

It was also an exciting time beyond the code: conferences, customer projects, and discussions around the world showed how relevant the ideas behind RAP really were. Special thanks go to Jochen Krause, whose entrepreneurial commitment, vision, and financial backing made this possible in the first place.

What makes me especially happy is that RAP is still around after 20 years, quietly and reliably doing its job. For the right kind of application, it remains a remarkably solid choice — and its server-side architecture still has practical qualities that remain relevant in today’s web landscape.

Happy birthday, RAP — and thanks to everyone who has kept it alive over all these years!”

— Frank Appel, RAP team lead and technical lead 2005–2008

A conference flyer from the early RAP days — "RAP the Web" — promoting the Rich Ajax Platform at eclipse.org, created by Innoopract.

Part 2: Building Trust – From Vision to Enterprise Reality

The true power of RAP lay in its promise of Single Sourcing: using the same codebase to create both a web-based (RAP) and a desktop (RCP) application. This was a game-changer, drastically reducing development and maintenance overhead for enterprises.

That promise was quickly put to the test. Early adopters came from some demanding sectors — telemedicine, energy management, trading systems — choosing RAP precisely because of its enterprise-grade reliability, OSGi modularity, and the ability to port complex existing RCP applications to the web without rewriting them from scratch.

Perhaps the most striking example of RAP’s reach into open source is Eclipse Scout, the application framework developed by BSI Business Systems Integration AG and donated to the Eclipse Foundation in 2011. Scout, a mature framework developed since 2001, added RAP-based web UI support in its 3.8 (Juno) release — a powerful signal that RAP had become a trusted foundation for serious enterprise frameworks, not just individual applications.

RAP’s longevity in enterprise settings reflects something Tim Buschtöns put well:

“RAP was the starting point of my professional career. It was the first open source project I ever worked on, and where I met many of the people I work with to this day. I learned more about software development working on RAP for a year than in all my studies combined. And on top of that, it outlived many projects I worked on since. I’m proud of what we accomplished with it, and I think it demonstrates that for many enterprises, proven and reliable technology that does exactly what you need can be more valuable than the shiny new thing that reinvents the wheel slightly more elegantly. I like that notion, because it means we can build technology that lasts.”

— Tim Buschtöns, EclipseSource developer

Part 3: Evolving Without Breaking – The Remote Application Platform

In 2013, with the release of RAP 2.0, something significant happened beyond a version number bump: the project changed its name. Rich Ajax Platform became Remote Application Platform — the acronym RAP remained the same, but the new name reflected a broader ambition. RAP was no longer just an AJAX framework; it was becoming a platform for any kind of remote client, communicating over a well-defined open JSON protocol. Native mobile clients for iOS and Android became possible alongside the browser client.

This kind of meaningful evolution — without breaking the applications already running on it — is exactly what enterprise customers need. And RAP delivered it.

It is worth pausing to appreciate what that means in practice. During RAP’s lifetime, entire generations of web technologies appeared, dominated the industry, and disappeared again. Frameworks that were industry standard when RAP 1.0 shipped are now largely forgotten. RAP quietly continued evolving through all of it, while preserving compatibility for the applications built on it. That kind of staying power is not accidental — it is the result of deliberate architectural choices and a sustained commitment to stability over novelty.

“I remember working on RAP when the first iPhone came out. JavaScript was still in its infancy, and none of today’s big web frameworks existed yet. A fellow on the team used to joke that ‘www’ stood for the ‘Wild Wild West’. Seeing a framework that started off in such a vastly different tech era still running stable and powering systems for major enterprise users today is simply incredible. Happy 20th anniversary, RAP!”

— Ralf Sternberg, former RAP project lead

Part 4: The Heart of Continuity – A Leadership Transition

The story of RAP isn’t just about technology; it’s about commitment across generations of contributors. In February 2016, Ralf Sternberg — who had been project lead since the early 2010s — stepped back to focus on Tabris.js, a project he had helped to kick off. In his farewell message to the rap-dev mailing list, he proposed Ivan Furnadjiev as an additional project lead, writing that Ivan is “probably the most knowledgeable person on the planet” when it comes to RAP. Ivan joined me as co-lead, and that is the arrangement we maintain to this day.

This transition wasn’t a disruption — it was a testament to the strength of the team. RAP is bigger than any single individual, and the project has the depth to carry itself forward for years to come.

Part 5: RAP by the Numbers

Twenty years of open source development leaves a traceable record. Here are some facts that speak for themselves:

• 69 releases shipped since RAP 1.0.0 in October 2007 through RAP 4.7.0 in June 2026, including service releases.
• Every single Eclipse Simultaneous Release from Ganymede (2008) onward has included RAP. That is an unbroken record of on-time delivery across more than 35 consecutive coordinated releases, spanning the named annual release trains from Ganymede through Photon, and every quarterly Eclipse Simultaneous Release since 2018 — most recently Eclipse IDE 2026-06.
• Nearly 10,000 commits in the GitHub repository, contributed by a team that has included over a dozen committers across two decades.
• Maven Central statistics show over 400 companies downloading RAP artifacts in a recent quarter, from more than 4,000 unique sources — a clear signal that RAP remains in active production use worldwide.

Maven Central download statistics for the org.eclipse.rap namespace, Q1 2026.

- The project website at [eclipse.dev/rap](https://eclipse.dev/rap) remains actively maintained, with documentation, demos, and downloads — the homepage of a living project, not an archive.

In the Eclipse world, shipping on time is a commitment taken seriously. RAP has never missed one.

“I was part of the RAP project from the very beginning until around 2009, back when it was still called the Rich Ajax Platform. The people I worked with on RAP had a lasting influence on how I approach technology, open source, and collaboration, and I’m grateful for that. I’m glad to see that RAP is still around 20 years later. It’s a reminder that technology built with care can evolve beyond its original scope and remain useful. Happy 20th anniversary, RAP!”

— Rüdiger Herrmann, early RAP committer

Part 6: RAP Today – Alive, Well, and Here to Stay

So, where does RAP stand on its 20th birthday?

Today, RAP is a proven, stable, and integral part of the Eclipse ecosystem. It still enables modular business applications for desktop, browser, and mobile. And EclipseSource is still here, maintaining it, evolving it, and supporting the enterprises that depend on it.

“Today we celebrate 20 years of the Eclipse Remote Application Platform (RAP) project. As the project lead and someone who has been involved since the very beginning, it has been an incredible journey to watch RAP evolve from an idea into a mature and trusted technology. My son was born in 2008, and over the years I often joked that RAP became my second child — growing, maturing, and constantly teaching me something new. Together with many contributors and users, we have built a platform that values stability, reliability, and long-term compatibility. Two decades later, RAP continues to empower applications used by companies around the world and remains a well-established part of the Eclipse ecosystem. I am grateful to everyone who contributed to its success and to the community that has supported it throughout the years. Seeing RAP still actively used and appreciated after 20 years is both rewarding and inspiring.”

— Ivan Furnadjiev, RAP project lead

This anniversary is not just a look back. It is a commitment. For our customers who have built their businesses on RAP — and there are many of you — we want you to know: we have been here for every release, every migration, and every challenge. And we will continue to be there — for as long as our customers and the community need us. If you need expert assistance with your RAP-based application, EclipseSource offers Developer Support and Sponsored Open Source Development — from remote coaching and bug fixes to getting missing features implemented directly upstream.

“Twenty years ago, we made a bet: that open source could build better infrastructure than any single company, and that a server-side Java web framework could outlast every frontend fashion. That bet paid off, for us and for the community - not because we predicted the future, but because we built it with the right people and the right values. Commercial Open Source was the key to this success. RAP is still here, solid, trusted—and it will be for as long as our customers need it.”

— Jochen Krause, founding RAP project lead, CEO of EclipseSource

Looking Ahead

Twenty years is a long time in software. So why does RAP still matter in 2026?

Java remains one of the dominant languages in enterprise software development. The ecosystems built around it — OSGi, Jakarta EE, the Eclipse platform — are still actively maintained and widely deployed. The organisations that chose RAP a decade ago did not do so on a whim; they chose it because it fit a real architectural need, and that need has not gone away.

Long-lived enterprise applications are, by their nature, conservative. They cannot afford to be rewritten every time the frontend landscape shifts. RAP’s server-side architecture — where application logic lives on the server and the client is a thin, protocol-driven layer — has practical advantages that are, if anything, more appreciated now than they were in 2006: centralised security, predictable deployment, no npm dependency chains, no JavaScript build tooling to maintain.

RAP continues to ship on the Eclipse simultaneous release schedule, continues to track the Java and OSGi platform, and continues to be maintained by the same team that has been doing so for years. There is no roadmap to announce here, and no promises to make beyond what the track record already shows. For applications that need a stable, proven foundation — RAP is still that foundation.

Thank You

From the creation review on June 21, 2006 and the first RAP 1.0 release in October 2007 to the robust platform it is today, the journey of Eclipse RAP has been remarkable. It stands as a shining example of how open-source collaboration, driven by a clear vision and a dedicated community, can create technology that endures.

A heartfelt thank you to every developer, contributor, and user who has been part of this journey — including everyone who filed a bug report, reviewed a patch, or simply kept their RAP application running in production. Your trust is what makes this project meaningful.

The source code and its full history live at github.com/eclipse-rap/org.eclipse.rap. The project is open for contributions — and we look forward to the next chapter together.