Eclipse Community Forums: e(fx)clipse » Help setting target platform for e4 + fx + emf forms

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 12:59

Eclipse User

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.

Re: Help setting target platform for e4 + fx + emf forms [message #1698452 is a reply to message #1698441]

Mon, 15 June 2015 14:57

Eclipse User

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.

Re: Help setting target platform for e4 + fx + emf forms [message #1698458 is a reply to message #1698452]

Mon, 15 June 2015 15:08

Eclipse User

the nightly one 2.0.0

and jdk 8u45 on eclipse mars

[Updated on: Mon, 15 June 2015 15:12] by Moderator

Re: Help setting target platform for e4 + fx + emf forms [message #1698464 is a reply to message #1698458]

Mon, 15 June 2015 15:20

Eclipse User

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

Re: Help setting target platform for e4 + fx + emf forms [message #1698465 is a reply to message #1698464]

Mon, 15 June 2015 15:22

Eclipse User

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 15:25] by Moderator

Re: Help setting target platform for e4 + fx + emf forms [message #1698473 is a reply to message #1698465]

Mon, 15 June 2015 16:57

Eclipse User

Well i guess they do package imports so they wire against our fake bundle! This means you need the adapter hooks as well

Re: Help setting target platform for e4 + fx + emf forms [message #1698474 is a reply to message #1698473]

Mon, 15 June 2015 17:02

Eclipse User

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

Re: Help setting target platform for e4 + fx + emf forms [message #1698479 is a reply to message #1698474]

Mon, 15 June 2015 17:43

Eclipse User

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

Re: Help setting target platform for e4 + fx + emf forms [message #1698480 is a reply to message #1698479]

Mon, 15 June 2015 17:53

Eclipse User

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 16:11] by Moderator

Re: Help setting target platform for e4 + fx + emf forms [message #1699276 is a reply to message #1698480]

Tue, 23 June 2015 04:18

Eclipse User

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

Re: Help setting target platform for e4 + fx + emf forms [message #1699283 is a reply to message #1699276]

Tue, 23 June 2015 04:47

Eclipse User

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

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

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Jun 24 06:57:48 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter