Slow deployment when running as Applet

  • lowecg
Posted: Tue, 03/16/2010 - 04:32

Hello,

I've just installed JFX plug-in and tried to add some code which was generated by the Flamingo tools to a JFX project. I got the code to compile okay (after a restart of Eclipse!) but when trying to deploy the application as an Applet I noticed that a number of jars from the JRE (rt.jar, sunjce_provider.jar etc) are included in the deployment and these are taking a *long* time to process through jarsigner etc, and ultimately the applet fails to launch. The application fires up fine as a regular JFX application.

Am I missing some element of configuration? Or is this a wee glitch?

Cheers,

Chris.

PS - Wow, first post! Thanks for releasing the JFX plugin, I'm looking forward to seeing how it shapes up.

‹ Maven and the Exadel Eclipse plugin Welcome! ›

Yes, you are the first one.

  • maxkatz
  • 02/17/10
  • Tue, 03/16/2010 - 07:43
  • Copy comment link

Yes, you are the first one. Welcome to the forum! It's fixed in nightly builds. I'm running build #29 and it works there - http://download.exadel.org/javafx_plugin/builds/nightly/

Thanks Max - the applets now

  • lowecg
  • 03/16/10
  • Wed, 03/17/2010 - 02:40
  • Copy comment link

Thanks Max - the applets now deploy very quickly although I'm still not able to get the app running but I'll create another forum post for that.

Cheers,

Chris.

Good to hear. Do let us know

  • maxkatz
  • 02/17/10
  • Wed, 03/17/2010 - 06:38
  • Copy comment link

Good to hear. Do let us know about the other issue.

Slow (and not functioning) applet deploy

  • bengt
  • 04/13/10
  • Tue, 04/13/2010 - 00:57
  • Copy comment link

I'm also having problems with slow deployment of applets. It takes forever to deploy. The same application deploys a lot faster via NetBeans. Also, the applet signing does not seem to work since the applet is not functional when it finally deploys. Again it works without problems in NetBeans. I can't seem to find anywhere where I can specify that the jar should be signed and that Pac200 should be used (like in NetBeans).

I'm using version 1.2.4 of the Eclipse plugin.

/Bengt

Please post a sample JavaFX

  • maxkatz
  • 02/17/10
  • Tue, 04/13/2010 - 04:44
  • Copy comment link

Please post a sample JavaFX script with which the problem is reproduced. Also, do you run as Applet or Java Web Start?

Problems with applet deployment

  • bengt
  • 04/13/10
  • Tue, 04/13/2010 - 23:37
  • Copy comment link

Hi again!

I'v tracked down the problem. It turns out that I had the following two jars present on my runtime classpath:

javafx-common-1.2.3.jar
javafxrt-1.2.3.jar

These are renamed when put into my maven repository but originates from the javafx 1.2.3 sdk. I need them at compile time for some java stuff on the client side (Async stuff). When I removed them from my runtime classpath the applet deployment works. I'm not sure why this is happening but it is no longer a problem for me since I only need them at compile time.

I do however, get some problems with the generated "dest" directory (which is being created when I deploy as an applet). I get some synchronisation probems with the file system when the directory is deleted which a simple "Refresh" don't seem to solve. Anyway, I think the generated directory should not be generated under the project's root but under "target" in a maven build and under "bin" otherwise. Ideally this would be configurable.

/Bengt