Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » e(fx)clipse » Help setting target platform for e4 + fx + emf forms
Help setting target platform for e4 + fx + emf forms [message #1698441] Mon, 15 June 2015 16:59 Go to next message
Derek Vasconcelos is currently offline Derek VasconcelosFriend
Messages: 12
Registered: February 2014
Junior Member
Hello,

I am currently trying to code an e4 application with javafx rendering, and came to an issue on target when trying to add emf forms to it.

I am following the guidelines of not using the 
import javafx.*
directives on manifests, but the bundles from 
org.eclipse.emf.ecp.view.sdk.fx.feature
use them so i added the 
org.eclipse.fx.runtime.min.feature.feature.group
to my target (along with the 
[org.eclipse.fx.runtime.e4fx.feature
) .

Eclipse validates the plugins on run configuration but when launching the application, when the handler calls the part object i get:
java.lang.ClassNotFoundException: javafx.scene.Node cannot be found by org.eclipse.emf.ecp.view.model.fx_1.5.0.201411161608


Thanks in advance.

Report message to a moderator

Re: Help setting target platform for e4 + fx + emf forms [message #1698452 is a reply to message #1698441] Mon, 15 June 2015 18:57 Go to previous messageGo to next message
Thomas Schindl is currently offline Thomas SchindlFriend
Messages: 6651
Registered: July 2009
Senior Member
What version of e(fx)clipse are you using?

Tom

On 15.06.15 18:59, Derek Vasconcelos wrote:
> Hello,
>
> I am currently trying to code an e4 application with javafx rendering,
> and came to an issue on target when trying to add emf forms to it.
>
> I am following the guidelines of not using the import javafx.*
> directives on manifests, but the bundles from
> org.eclipse.emf.ecp.view.sdk.fx.feature use them so i added the
> org.eclipse.fx.runtime.min.feature.feature.group to my target (along
> with the [org.eclipse.fx.runtime.e4fx.feature) .
>
> Eclipse validates the plugins on run configuration but when launching
> the application, when the handler calls the part object i get:
>
> java.lang.ClassNotFoundException: javafx.scene.Node cannot be found by
> org.eclipse.emf.ecp.view.model.fx_1.5.0.201411161608
> Thanks in advance.

Report message to a moderator

Re: Help setting target platform for e4 + fx + emf forms [message #1698458 is a reply to message #1698452] Mon, 15 June 2015 19:08 Go to previous messageGo to next message
Derek Vasconcelos is currently offline Derek VasconcelosFriend
Messages: 12
Registered: February 2014
Junior Member
the nightly one 2.0.0

and jdk 8u45 on eclipse mars

[Updated on: Mon, 15 June 2015 19:12]

Report message to a moderator

Re: Help setting target platform for e4 + fx + emf forms [message #1698464 is a reply to message #1698458] Mon, 15 June 2015 19:20 Go to previous messageGo to next message
Thomas Schindl is currently offline Thomas SchindlFriend
Messages: 6651
Registered: July 2009
Senior Member
So do you launch with -Dorg.osgi.framework.bundle.parent=ext?

Tom

On 15.06.15 21:08, Derek Vasconcelos wrote:
> the nightly one 2.0.0

Report message to a moderator

Re: Help setting target platform for e4 + fx + emf forms [message #1698465 is a reply to message #1698464] Mon, 15 June 2015 19:22 Go to previous messageGo to next message
Derek Vasconcelos is currently offline Derek VasconcelosFriend
Messages: 12
Registered: February 2014
Junior Member
yes
<stringAttribute key="org.eclipse.jdt.launching.VM_ARGUMENTS" value="-Dorg.osgi.framework.bundle.parent=ext"/>


Should i launch without it?

my full launch is:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<launchConfiguration type="org.eclipse.pde.ui.RuntimeWorkbench">
<setAttribute key="additional_plugins"/>
<booleanAttribute key="append.args" value="true"/>
<booleanAttribute key="askclear" value="true"/>
<booleanAttribute key="automaticAdd" value="false"/>
<booleanAttribute key="automaticValidate" value="true"/>
<stringAttribute key="bootstrap" value=""/>
<stringAttribute key="checked" value="[NONE]"/>
<booleanAttribute key="clearConfig" value="true"/>
<booleanAttribute key="clearws" value="true"/>
<booleanAttribute key="clearwslog" value="false"/>
<stringAttribute key="configLocation" value="${workspace_loc}/.metadata/.plugins/org.eclipse.pde.core/br.unicamp.cepetro.unisim.mero.app.product.product"/>
<booleanAttribute key="default" value="false"/>
<stringAttribute key="featureDefaultLocation" value="workspace"/>
<stringAttribute key="featurePluginResolution" value="workspace"/>
<booleanAttribute key="includeOptional" value="true"/>
<stringAttribute key="location" value="${workspace_loc}/../runtime-br.unicamp.cepetro.unisim.mero.app.product"/>
<booleanAttribute key="org.eclipse.jdt.launching.ATTR_USE_START_ON_FIRST_THREAD" value="true"/>
<stringAttribute key="org.eclipse.jdt.launching.JRE_CONTAINER" value="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.8"/>
<stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS" value="-nl ${target.nl} -consoleLog -nosplash -console -clearPersistedState"/>
<stringAttribute key="org.eclipse.jdt.launching.SOURCE_PATH_PROVIDER" value="org.eclipse.pde.ui.workbenchClasspathProvider"/>
<stringAttribute key="org.eclipse.jdt.launching.VM_ARGUMENTS" value="-Dorg.osgi.framework.bundle.parent=ext"/>
<stringAttribute key="pde.version" value="3.3"/>
<stringAttribute key="product" value="br.unicamp.cepetro.unisim.mero.app.product"/>
<stringAttribute key="productFile" value="/br.unicamp.cepetro.unisim.mero.app.product/br.unicamp.cepetro.unisim.mero.app.product.product"/>
<setAttribute key="selected_features">
<setEntry value="br.unicamp.cepetro.unisim.mero.app.feature:default"/>
<setEntry value="org.eclipse.emf.ecp.emfforms.runtime.feature:default"/>
<setEntry value="org.eclipse.fx.runtime.e4fx.feature:default"/>
<setEntry value="org.eclipse.fx.runtime.min.feature:default"/>
</setAttribute>
<booleanAttribute key="show_selected_only" value="false"/>
<booleanAttribute key="tracing" value="false"/>
<booleanAttribute key="useCustomFeatures" value="true"/>
<booleanAttribute key="useDefaultConfig" value="true"/>
<booleanAttribute key="useDefaultConfigArea" value="true"/>
<booleanAttribute key="useProduct" value="true"/>
<booleanAttribute key="usefeatures" value="false"/>
</launchConfiguration>

[Updated on: Mon, 15 June 2015 19:25]

Report message to a moderator

Re: Help setting target platform for e4 + fx + emf forms [message #1698473 is a reply to message #1698465] Mon, 15 June 2015 20:57 Go to previous messageGo to next message
Thomas Schindl is currently offline Thomas SchindlFriend
Messages: 6651
Registered: July 2009
Senior Member
Well i guess they do package imports so they wire against our fake bundle! This means you need the adapter hooks as well

Report message to a moderator

Re: Help setting target platform for e4 + fx + emf forms [message #1698474 is a reply to message #1698473] Mon, 15 June 2015 21:02 Go to previous messageGo to next message
Derek Vasconcelos is currently offline Derek VasconcelosFriend
Messages: 12
Registered: February 2014
Junior Member
Darn Sad
I dont like the idea of going against the most recent conventions, so i shall abort the emf forms usage for now. Is there any other alternative to make editors bound to an emf model in an easy manner? I know efxclipse has some emf features but i didnt find much documentation on usage

Report message to a moderator

Re: Help setting target platform for e4 + fx + emf forms [message #1698479 is a reply to message #1698474] Mon, 15 June 2015 21:43 Go to previous messageGo to next message
Thomas Schindl is currently offline Thomas SchindlFriend
Messages: 6651
Registered: July 2009
Senior Member
As I've never used EMF-Forms myself all i say is speculative! Have you
asked at their forum?

If they are doing package imports they should stop doing so or at least
mark them optional because this would allow you to run with the
min.feature and things would still work!

Did using "-Dosgi.framework.extensions=org.eclipse.fx.osgi
-Dorg.osgi.framework.bundle.parent=ext" fix the problems?

As of today the best other option is to use EMF-Databinding and
JavaFX-Eclipse-Databinding but this means you need to craft your UI by
hand or eg through SceneBuilder.

Tom

On 15.06.15 23:02, Derek Vasconcelos wrote:
> Darn :(
> I dont like the idea of going against the most recent conventions, so i
> shall abort the emf forms usage for now. Is there any other alternative
> to make editors bound to an emf model in an easy manner? I know
> efxclipse has some emf features but i didnt find much documentation on
> usage

Report message to a moderator

Re: Help setting target platform for e4 + fx + emf forms [message #1698480 is a reply to message #1698479] Mon, 15 June 2015 21:53 Go to previous messageGo to next message
Derek Vasconcelos is currently offline Derek VasconcelosFriend
Messages: 12
Registered: February 2014
Junior Member
I'm interested on doing the interface on the fxgraph/fxml + databinding way. Is there any source i could checkout that contains examples on this?

[Updated on: Thu, 18 June 2015 20:11]

Report message to a moderator

Re: Help setting target platform for e4 + fx + emf forms [message #1699276 is a reply to message #1698480] Tue, 23 June 2015 08:18 Go to previous messageGo to next message
Eugen Neufeld is currently offline Eugen NeufeldFriend
Messages: 174
Registered: May 2015
Senior Member
Hi Derek, Hi Tom,

We are using package imports in our bundles. This was the way the example did it in version 1.0.0 and 1.1.0 of e(fx)clipse.
As the EMFForms implementation for JavaFX never found any (known) users we kept it on maintenance.
Would it be enough to change the package imports to bundle imports?
We would happily accept a contribution and provide any help needed.

Cheers,
Eugen

--
Eugen Neufeld

Get professional Eclipse developer support:
http://eclipsesource.com/en/services/developer-support/

Report message to a moderator

Re: Help setting target platform for e4 + fx + emf forms [message #1699283 is a reply to message #1699276] Tue, 23 June 2015 08:47 Go to previous message
Thomas Schindl is currently offline Thomas SchindlFriend
Messages: 6651
Registered: July 2009
Senior Member
In 2.x you don't need any package imports at all!

Our advice for > 2.x is:
* in RCP use -Dorg.osgi.framework.bundle.parent=ext
* in Plugin-Dev use the adapter hooks
=> they have changed in 2.x to work as a last resort strategy
so they work with/without package imports!

Tom

On 23.06.15 10:18, Eugen Neufeld wrote:
> Hi Derek, Hi Tom,
> We are using package imports in our bundles. This was the way the
> example did it in version 1.0.0 and 1.1.0 of e(fx)clipse.
> As the EMFForms implementation for JavaFX never found any (known) users
> we kept it on maintenance. Would it be enough to change the package
> imports to bundle imports?
> We would happily accept a contribution and provide any help needed.
>
> Cheers,
> Eugen

Report message to a moderator

Previous Topic:Eclipse 3.* plugin issues when trying to create a stage.
Next Topic:l10n files generate a gitignore file ?
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Mon Jan 20 03:24:01 GMT 2025

Powered by FUDForum. Page generated in 0.03211 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly