Programmable platform X ships to customers with a complete development environment, with various editors for aspects of X's functionality.
The company (and maybe 3rd parties) sell separate add-on components for X, each of which comes with its own programming tools.
These add-on tools, when purchased, must dynamically and smoothly integrate with those of X. The editors show up in menus and extend the list of file-types that
can be developed, the documentation becomes another chapter in the on-line manual, and the builders and runners add themselves to the development infrastructure. Personalization apply to the new "layer" without other change.
Both X, and the licensed add-on tools must be independently upgradable. Restarting X every time is not an option.
--
Chaim
From: che-dev-bounces@xxxxxxxxxxx [mailto:che-dev-bounces@xxxxxxxxxxx]
On Behalf Of Tyler Jewell
Sent: Thursday, July 30, 2015 4:46 PM
To: che developer discussions
Subject: Re: [che-dev] Dynamic updating of Che extensions
We had a chance to discuss this internally.
We do not have much to share. We think it may be possible with server-side extensions, but there would be many questions that have to be investigated and answered. The server-side depends upon
Guice dependency injection and we aren't sure what the impacts of dynamic classloading and extension reloading would be on that. We are not in a position to do a deep dive investigation on this topic until after we ship the 4.x release later this year. We
are not yet in a position where we even have all of the questions that we should be asking. It's one of those situations where we need to sink our teeth into this for a few weeks so that we can come back with a clear understanding of the problem at hand.
So the conclusion is that we think it should be possible, it's wading into some tricky waters, and we'd need an extended period of investigation + implementation time to make it solid.
Can you tell us more about the problem that you are attempting to solve with dynamic extension deployment?
On Tue, Jul 28, 2015 at 11:13 PM, Soffer, Guy <guy.soffer@xxxxxxx> wrote:
Hi Tyler,
A timeframe for the analysis would be around a month or two. We are specifically interested in server-side
extensions as we don't use GWT.
Would be glad to hear your thoughts and plans once you've something to share.
Thanks in advance,
Guy
Feed: che-dev
Posted on: Wednesday 29 July 2015 02:50
Author: tyler@xxxxxxx (Tyler Jewell)
Subject: Re: [che-dev] Dynamic updating of Che extensions
We have the question and are thinking it through. We do not have well-evolved thoughts here. This question has come up from time to
time, but we haven't done the prepatory work to have a clear design of the approach that we would take.
One thought that we have to explore is if we can have a different form of extension update for server-side extensions vs. client-side
extensions, which have to be compiled into a GWT application.
Do you have a timeframe for your analysis? We will huddle on our side for a dialog.
On Mon, Jul 27, 2015 at 8:00 AM, Soffer, Guy <guy.soffer@xxxxxxx> wrote:
Hi all,
Â
For SAP Che implementation we're now exploring the extensibility story. I understand that currently there is no way to update extensions dynamically. As this is something we would
like to support in the future, I have some related questions:
ÂÂÂÂÂÂÂÂÂ
Do you have plans to support this in the future?
ÂÂÂÂÂÂÂÂÂ
As incremental changes in a running container during extension development are supported, can you provide some details how is it done?
ÂÂÂÂÂÂÂÂÂ
Any suggestions how to implement this for productive usage in the current Che implementation?
Â
Thanks in advance,
Â
Guy Soffer
Area Architect, SAP Web IDE
P&I Tech Cloud Experience
SAP Labs Israel
15 Hatidhar St., Ra'anana 4366517, Israel
TÂÂÂÂ
+972-9-777-9581
FÂÂÂÂ
+972-74-760-9581
MÂÂÂ
+972-54-301-3000
|
_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/che-dev
|
