JavaFX 2 and OSGi-Deployment models

It looks like a lot of people are interested in using JavaFX into one of their Eclipse Views. I infer that from the people visiting my blog from a stackoverflow question. The problem people face is that in Eclipse JavaFX has to run in an OSGi-Environment and JavaFX is not prepared for that leading to all sorts of problems when one applies the standard strategies (e.g. simply repackaging the javafx.jar as an OSGi-Bundle). I'm happy to announce that the upcoming e(fx)clipse release 0.0.13 will fix your problems and make it very easy to use JavaFX inside your Eclipse Views. The important changes that went into 0.0.13 is that different deployment models are going to be supported:

• System installation: This deployment model requires your users to have JavaFX pre-installed on their system
• Next to your app installation: This deployment model requires you to place javafx next to your RCP/IDEs launcher - similar to how you can deploy a JRE with your Eclipse Application
• As a bundle installation: Here you place your javafx.jar into an OSGi-Bundle and the e(fx)clipse runtime will take care of extracting and wireing

If you want to see it in action you can download a self-contained win32/32bit version of a RCP using this link which uses the 3rd deployment strategy. The sources are checked into the e(fx)clipse git-repo. Once 0.0.13 is released (which is going to be next weekend) I hope I can come up with a tutorial.