Hello, folks!
First of all, big thank you, Che Team, for such a great work! At our company we are playing with deep Che customizations. It’s very interesting!
But it’s quickly become clear for us that WAR monolithic deployment troubles Che modules reusability in case of deep customizations.
Different modularity technologies in Eclipse RCP and Eclipse Che (OSGi vs WAR) limit Eclipse RCP/IDE/MDD bundles reusability inside Che environment.
On the other side, we’ve seen recent Liferay success in adopting OSGi and DS for huge monolithic WAR portal modularization.
https://www.eclipsecon.org/europe2015/sites/default/files/slides/EclipseCon%20Europe%202015_Liferay%20Modularity%20Patterns_Rafik%20HARABI_v1.0.pdf
So, my questions to the core developers and adopters:
- Do you have some long-term plans of adopting OSGi and DS to modularize monolithic WAR portal, to make Che even more flexible and reusable?
- Is someone here interested to evolve Che in this direction?
We have some initial prototypes of server-side Che modules as OSGi Declarative Services without any server-side dependencies on top of Equinox+Jetty+Jersey+ECF container. And we wonder if it’s interesting for someone?
---
WBW,
Alexey Ivanov
