- Separate model and UI bundles
- Tweak the preference handling (avoid the "org.eclipse.jface" dependency in the model bundle)
- Find a solution for the Eclipse extension point registry
- Create a web bundle to access your application
If the RCP application is designed well, it's no problem to re-use the model bundles for the web. Because we rely on OSGi!
For instance, Eclipse Virgo offers great capabilities to run the model bundles and the servlets to access the applications functionality. We'll have a look at the a combination with the following server side technologies:
* Eclipse Virgo
* OSGi enRoute
* Spring Boot
Finally, both RCP and Web application are build using Maven/Tycho without making additional rendering engine modifications. You stay in one workspace, which makes refactorings comfortable.
Hence, a combination of both worlds is not just only possible, it keeps you flexible for decisions in the future.