Thanks for the advise.
I also took the conservative approach in wrapping the SDK. Only the jars javafxc, javafxrt, Scenario and javafxgui are wrapped in one jar. Do you bundle them as well as one or as separate? That was not clear from the maven code, given my limited knowledge of maven. The framework_systempackages_extra are not set when adding the SDK as a bundle. The exception is thrown by the jfx code and does not come more informative that this I am affraid. Bundle 1 is a helloworld bundle to see if the framework behaves as expected, bundle 2 is the jfx sdk and bundle 3 is the application.

Eelco

On May 14, 2009, at 3:36 PM, Patrick Forhan wrote:

Well, don't try to tackle too many things at once... you'll need a
firm understanding of OSGi and JavaFX separately from one another in
order to be really effective.  Maven-vs-ant shouldn't matter too much
at this point, though it does seem like the maven-bundle-plugin (which
uses BND) has been getting a lot of attention and features.

I found I had to be careful in bundling up the JavaFX stuff... if I
took too much, the bundle would start having dependencies on more and
more things, which would in turn require more bundles.  You should be
able to adapt the bundle-instructions I used in maven to make a
similar bundle via ant or BND.  I think we got it to the point where
it only had JRE dependencies.  We also cheated and made a bunch of
things optional imports when they probably weren't entirely, like
applet, javascript, and media support.

It's hard to debug from here as to your problem with bundle 3 (is that
your JFX code, or the runtime?).  Also, if you bundle up javafx, you
shouldn't need framework_systempackages_extra or the jfx stuff in your
startup classpath.

Pat.

--
Defy mediocrity.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



Wageningen University
Plant Production Systems
P.O. Box 430
6700 AK WAGENINGEN
The Netherlands
http://www.pps.wur.nl






---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to