|[EMF Forms] Move from 1.9 to 1.17 [message #1790663]
||Thu, 14 June 2018 07:15
| Andre Doerscheln
Registered: June 2015
We're currently trying to finally update our dependencies to the very latest versions. This includes RAP (3.1 -> 3.5) and EMFForms (1.9 -> 1.17).
We're currently facing the issue that some Components loose their references, when Activators assign them. To give you an example, this happens with the EMFFormsLabelProvider, which is used in the org.eclipse.emf.ecp.edit.internal.swt.Activator singleton. It get's requested by getEMFFormsLabelProvider() and is then unget by the same method. When the LabelProvider stored in the singleton is then used, there are no references anymore, because of ungetting it earlier, which leads Equinox to throw it away.
As a workaround we're currently requesting the same service via the BundleContext upfront to increase the useCount, so that Equinox is not throwing it away when ungetting the service.
I don't think it should be like this. Do i miss something? How is this supposed to work?
What we're using:
- ECP/EMFForms 1.17.0 (self-build from tag, minor customizations)
- Eclipse RAP 3.5
Dependencies are coming from
- the latest Photon Orbit (R20180606145124)
- EPP Photon update site (http://download.eclipse.org/technology/epp/packages/photon/)
- Eclipse Photon update site (http://download.eclipse.org/releases/photon/)
Edit: We're still using e3.
[Updated on: Thu, 14 June 2018 08:07]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.02388 seconds