Eclipse Community Forums: e(fx)clipse » Extension point org.eclipse.e4.workbench.model doesn't work anymore

Help

Home

Home » Eclipse Projects » e(fx)clipse » Extension point org.eclipse.e4.workbench.model doesn't work anymore

Show: Today's Messages :: Show Polls :: Message Navigator

Extension point org.eclipse.e4.workbench.model doesn't work anymore [message #1853339]

Tue, 28 June 2022 12:35

Robert Pöchtrager

Messages: 2
Registered: June 2022

Junior Member

Hi,

since the changes in org.eclipse.e4.ui.internal.workbench.ModelAssembler.processModel(boolean) because of https://bugs.eclipse.org/bugs/show_bug.cgi?id=571866 the extension point org.eclipse.e4.workbench.model of my JavaFX application doesn't work anymore, because the IExtensionRegistry is not set.

It's working when i set the Registry in org.eclipse.fx.ui.workbench.base.internal.EFX_ResourceHandler.loadMostRecentModel() like
ModelAssembler contribProcessor = ContextInjectionFactory.make(ModelAssembler.class, this.context); contribProcessor.setExtensionRegistry(Platform.getExtensionRegistry());
contribProcessor.processModel(initialModel);

Is there another easy solution I'm overlooking?

Thanks
Robert

Report message to a moderator

Re: Extension point org.eclipse.e4.workbench.model doesn't work anymore [message #1853348 is a reply to message #1853339]

Tue, 28 June 2022 18:40

Thomas Schindl

Messages: 6650
Registered: July 2009

Senior Member

I guess you are talking about the current snapshots? I wonder if we need our own resourceloader or we simply switch to the default one (if all regression there have been fixed and new one did not get integrated)

[Updated on: Tue, 28 June 2022 18:41]

Report message to a moderator

Re: Extension point org.eclipse.e4.workbench.model doesn't work anymore [message #1853357 is a reply to message #1853348]

Wed, 29 June 2022 05:58

Robert Pöchtrager

Messages: 2
Registered: June 2022

Junior Member

It is working with Eclipse 2020-12 (4.18) and e(fx)clipse 3.8, since 2021-06 (4.20) + 3.8 the error occurs.

In my case you are right because of the own resource loader, I tried the org.eclipse.e4.ui.internal.workbench.ResourceHandler and it is working.

Thank you

Report message to a moderator