Does launching an applet via JNLP work on Linux at all?
in [Java Help]
|
Prev: Java Swing Question: Robot Screenshot does odd things when closeto the mouse cursor
Next: Java crash
From: Qu0ll on 26 Feb 2010 04:12 "Qu0ll" <Qu0llSixFour(a)gmail.com> wrote in message news:UP2dnetahbwelBvWnZ2dnUVZ_t-dnZ2d(a)westnet.com.au... [...] > OK, I have stripped out all the IP-sensitive material and produced a very > simple example for others to test. [...] > Please let me know of your results. Hopefully someone can see why it is > not working on Linux. My assumption that it doesn't work at all on Linux is in fact incorrect as today I tried it on a 64-bit CentOS 5.3 installation with 64-bit Java 6u10 and it worked in Firefox 3.0.14. Now, reading the release notes for 6u18 I see that support for Ubuntu 8.10 was added so perhaps Ubuntu 9.10 will simply not support JNLP launched applets, at least not yet. I don't know what the difference would be but there you go. It would be nice if someone could confirm that it does indeed work on Ubuntu 8.10 with 6u18(?). Anyway, I decided to try using a simpler APPLET tag in the HTML instead of deployJava.runApplet and now I am back to where I was in August 2009 [1] namely getting a CNFE on DownloadServiceListener instead of the applet's class. So it seems that launching applets via JNLP still doesn't work in many places and that there is something wrong with deployJava.js in relation to launching applets. This is all exceedingly frustrating and makes it tempting to abandon client-side Java altogether. The major part of Java's attraction as a web client deployment platform is that the applet runs unchanged on all OSes in all browsers. Clearly this is just not even close to being true. So why should I keep using client-side Java? Well sure, I've invested hundreds of hours work into it but if it doesn't work in the most popular Linux flavour and doesn't work in Opera or Safari or on Solaris etc. etc. then have I been wasting my time? Flash has its detractors but it's looking very attractive right now :-( [1] http://www.javakb.com/Uwe/Forum.aspx/java-programmer/47851/Lazy-applet-JAR-downloading-using-JNLP-Part-II -- And loving it, -Qu0ll (Rare, not extinct) _________________________________________________ Qu0llSixFour(a)gmail.com [Replace the "SixFour" with numbers to email me]
From: Andrew Thompson on 26 Feb 2010 04:29 On Feb 25, 4:24 pm, "Qu0ll" <Qu0llSixF...(a)gmail.com> wrote: > "Qu0ll" <Qu0llSixF...(a)gmail.com> wrote in message >.. > <jnlp spec="6.0+" codebase="." href="applet.jnlp"> Embedded JNLP applets should not include a codebase attribute. -- Andrew T. pscode.org
From: Andrew Thompson on 26 Feb 2010 04:39 On Feb 25, 1:08 am, Lew <no...(a)lewscanon.com> wrote: > Roedy Green wrote: > > On Wed, 24 Feb 2010 18:14:28 +1100, "Qu0ll" <Qu0llSixF...(a)gmail.com> > > wrote, quoted or indirectly quoted someone who said : > > >> So, does launching an applet (yes, applet) using JNLP work at all on Linux? > >> In all cases I am using Java 6 Update 18. > > > If you are running 64 bit Linux, you will need to install both 32- bit > > and 64-bit Java. JNLP uses 32-bit, to match the power of the browser. > > Umm, I'm running 64-bit Java 6u18, Ubuntu and browsers, and Java Web Start > works just fine for applications. Applets also work fine. I haven't tried > applets launched via JNLP. Huhh.. When I changed over to Ubuntu Linux, I specifically chose the 32 bit JRE on the understanding that 64 bit did not support applets & JWS! And as an aside, I have never been able to coax the FF/32 bit JRE combo. that I have, into recognising *any* damn embedded JNLP based applet. I think it's time to uninstall every gosh-darn JRE that I have (including, by mistake, a download of the Open JDK) and try the 64 bit version. Thanks for the heads up. :-) -- Andrew T. pscode.org
From: Qu0ll on 26 Feb 2010 05:03 "Andrew Thompson" <andrewthommo(a)gmail.com> wrote in message news:52672078-07e3-4fb1-8908-8a7285600c71(a)s25g2000prd.googlegroups.com... > On Feb 25, 4:24 pm, "Qu0ll" <Qu0llSixF...(a)gmail.com> wrote: >> "Qu0ll" <Qu0llSixF...(a)gmail.com> wrote in message >>.. >> <jnlp spec="6.0+" codebase="." href="applet.jnlp"> > > Embedded JNLP applets should not include a codebase > attribute. I included that only out of desperation. It doesn't work with or without. -- And loving it, -Qu0ll (Rare, not extinct) _________________________________________________ Qu0llSixFour(a)gmail.com [Replace the "SixFour" with numbers to email me]
From: John B. Matthews on 26 Feb 2010 06:03
In article <q0beo5tm381mnlki33j1oqnm69tq94kpms(a)4ax.com>, Roedy Green <see_website(a)mindprod.com.invalid> wrote: > if the Javascript stuff is not working (which in my experience > happens about 20% of the time), bypass it with > > <a href="applet.jnlp">Launch</a> This seems like a reasonable alternative, if I interpret this comment in deployJava.js correctly: "Chrome, Safari, and Opera browsers find the plugin but it doesn't work, so until we can get it to work - don't use it." <http://java.com/js/deployJava.txt> -- John B. Matthews trashgod at gmail dot com <http://sites.google.com/site/drjohnbmatthews> |