|Re: AbstractFXEditor throws ClassNotFoundException via o.e.g.mvc.fx.ui [message #1783594 is a reply to message #1782934]
||Wed, 14 March 2018 13:01
|| Stephan Druskat
Registered: October 2011
Location: Berlin, Germany
So in the end I decided to roll back to using AbstractFXEditor for convenience, and I managed to get that setup to work as well, without having to resort to the dreaded BuddyPolicy.|
Based on Dirk Fauth's cookbook recipe (thanks Dirk, not only did you give us NatTable, but also saved my day with this recipe), I did the following:
- Add the e(fx)clipse E4 Target feature to the target definition (org.eclipse.fx.target.rcp4.feature.feature.group, from http://download.eclipse.org/efxclipse/runtime-released/2.6.0/site/)
- Add the feature to the product definition
- Add the VM argument -Dosgi.framework.extensions=org.eclipse.fx.osgi to the product definition
Note that I didn't have to import any javafx* packages (in fact, when I did, I got the "deprecated binding" warning WARNING: You are binding against the deprecated org.eclipse.fx.javafx - please remove all javafx imports).
Works like a spell!
UPDATE: Well, works like a spell after I've changed -Dosgi.framework.extensions=org.eclipse.fx.osgi to -Dorg.osgi.framework.bundle.parent=ext. Funnily enough, the former works fine on Linux OpenJDK, the latter is needed for Windows 10 and Oracle JDK.
[Updated on: Wed, 14 March 2018 19:52]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.64514 seconds