Eclipse Community Forums: Eclipse 4 » Model fragment merge on plugin installation

Home » Eclipse Projects » Eclipse 4 » Model fragment merge on plugin installation

Model fragment merge on plugin installation [message #900995]

Thu, 09 August 2012 07:18

Eclipse User

Hi there,

is my understanding correct that model fragments are only merged into the application model on platform startup?
My problem is that I have to support plugin installation/deinstallation without restart. Is there any way to unmerge model contributions on deinstall and merge on install?

Thanks in advance,
Axel

P.S: I really enjoy working with e4!

Re: Model fragment merge on plugin installation [message #901001 is a reply to message #900995]

Thu, 09 August 2012 07:33

Eclipse User

Right we currently only merge in stuff when application framework starts
up. The code is in the ModelAssembler and you can most likely reuse the
logic there.

What we currently not have is the opposite - removing fragments at
runtime but we already track where a contribution has been coming from
so removing contributed elements should be doable also.

I'd approch the problem of dynamic loading/unloading by registering an
Addon which listens to bundles coming and going. We naturally accept
patches who bring this feature to framework itself as well ;-)

Tom

Am 09.08.12 13:18, schrieb Axel Ruder:
> Hi there,
>
> is my understanding correct that model fragments are only merged into
> the application model on platform startup?
> My problem is that I have to support plugin installation/deinstallation
> without restart. Is there any way to unmerge model contributions on
> deinstall and merge on install?
>
> Thanks in advance,
> Axel
>
> P.S: I really enjoy working with e4!

Re: Model fragment merge on plugin installation [message #901010 is a reply to message #901001]

Thu, 09 August 2012 07:57

Eclipse User

Thanks Tom for the quick answer!

I'll give it a shot Wink

!

Axel

Re: Model fragment merge on plugin installation [message #901024 is a reply to message #901001]

Thu, 09 August 2012 09:01

Eclipse User

An other work around you might want to try is through the use of a processor. If you register a processor (instead of a fragment) it is loaded at the same time a fragment is. Since you have programmatically defined your model elements, you could add something to the Activator.stop() and remove all of the elements added.

This is more of a hack, I don't really like adding too many things to the start/stop methods. Tom's solution is the ideal approach, but this is another option. Smile

Previous Topic:	JSP format before saving
Next Topic:	e4 Creating a window with NO_TRIM

Goto Forum:

-=] Back to Top [=-

Current Time: Fri Jul 25 18:01:44 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter