Eclipse Community Forums: e(fx)clipse » e(fx)clipse issue compiling w/ RoboVM

Home » Eclipse Projects » e(fx)clipse » e(fx)clipse issue compiling w/ RoboVM(Getting a ClassCastException while compiling e(fx)clipse app with RoboVM)

e(fx)clipse issue compiling w/ RoboVM [message #1404675]

Mon, 04 August 2014 19:09

Eclipse User

I'm Creating an iOS app using e(fx)clipse and RoboVM (bundled with the efx), and I'm getting a consistent ClassCastException while performing the FXML compilation process:

/Work/Eclipse/Four/robovm-build/robovm-ant.xml:83: java.lang.ClassCastException: org.eclipse.fx.ide.fxgraph.fXGraph.impl.PropertyImpl cannot be cast to org.eclipse.fx.ide.fxgraph.fXGraph.Element

My Ant file is the default one generated by the RoboVM project generation tool. It crashes on the FXML compilation line:

<fxml-compiler sourcedir="build/src" destdir="build/gen-src"/>

There is no stacktrace, unfortunately. Works perfectly with the Java-based Mobile Simulator, but when compiled with RoboVM to run on iOS simulator, it aborts with the ClassCastException.

Any ideas what may be causing this error?

Thanks!

Re: e(fx)clipse issue compiling w/ RoboVM [message #1404782 is a reply to message #1404675]

Tue, 05 August 2014 13:11

Eclipse User

This shoulds like a problem in the FXML => Java translation. Can you
provide the FXML-File used as the input? What version of e(fx)clipse are
you using?

Tom

On 05.08.14 15:53, Mario Wunderlich wrote:
> I'm Creating an iOS app using e(fx)clipse and RoboVM (bundled with the
> efx), and I'm getting a consistent ClassCastException while performing
> the FXML compilation process:
>
> /Work/Eclipse/Four/robovm-build/robovm-ant.xml:83:
> java.lang.ClassCastException:
> org.eclipse.fx.ide.fxgraph.fXGraph.impl.PropertyImpl cannot be cast to
> org.eclipse.fx.ide.fxgraph.fXGraph.Element
>
>
>
> My Ant file is the default one generated by the RoboVM project
> generation tool. It crashes on the FXML compilation line:
> <fxml-compiler sourcedir="build/src" destdir="build/gen-src"/>
>
> There is no stacktrace, unfortunately. Works perfectly with the
> Java-based Mobile Simulator, but when compiled with RoboVM to run on iOS
> simulator, it aborts with the ClassCastException.
>
> Any ideas what may be causing this error?
>
> Thanks!

Re: e(fx)clipse issue compiling w/ RoboVM [message #1404848 is a reply to message #1404782]

Tue, 05 August 2014 22:15

Eclipse User

The problem seems to appear only when I'm using include ... from fxgraph (<fx:include ... />) if I copy-paste all contents into a single FXML file instead of including, the error goes away.

I'm using e(fx)clipse 0.9.0 with Eclipse 4.3.2 SDK

Attached the FXML (generated from fxgraph) files.

Thanks,
Mario

Attachment: Container.fxml
(Size: 0.92KB, Downloaded 212 times)
Attachment: StandardButtons.fxml
(Size: 0.76KB, Downloaded 207 times)
Attachment: Sidebar.fxml
(Size: 0.53KB, Downloaded 226 times)
Attachment: ScreenOne.fxml
(Size: 0.73KB, Downloaded 173 times)

Re: e(fx)clipse issue compiling w/ RoboVM [message #1404924 is a reply to message #1404848]

Wed, 06 August 2014 02:47

Eclipse User

Hi,

Yeah - includes are not yet supported by the FXML => Java translation.
We've started working on support for them already but it looks like the
co-worker did not yet finished the support in time for 1.0 [1].

In 1.1 I plan to revise the RoboVM and Android support, we are currently
bundleing a fairly old version of RoboVM and a rather old JavaFX build,
I plan to switch this to http://javafxports.org/page/Getting_Started.

Tom

[1]https://bugs.eclipse.org/bugs/show_bug.cgi?id=432226

On 06.08.14 04:15, Mario Wunderlich wrote:
> The problem seems to appear only when I'm using include ... from fxgraph (<fx:include ... />) if I copy-paste all contents into a single FXML file instead of including, the error goes away.
>
> I'm using e(fx)clipse 0.9.0 with Eclipse 4.3.2 SDK
>
> Attached the FXML (generated from fxgraph) files.
>
> Thanks,
> Mario
>

Re: e(fx)clipse issue compiling w/ RoboVM [message #1406007 is a reply to message #1404924]

Fri, 08 August 2014 15:00

Eclipse User

Hi,

Yea I figured as much. It will be awesome to have FXML includes, but in the meantime I'll create a quick workaround to get our project going. This is great tool for mobile dev, I can't wait to try out the next version.

Best regards,
Mario

Previous Topic:	Console Error Output when using FXCanvas
Next Topic:	CSS compare dialog: 1.0.0.201408081420 - Editor could not be initialized

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Apr 19 13:38:48 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter