CNET: Google begins barring browser plug-ins from Chrome

[Joe McGlynn]

Applets, whether old-school applets that are deployed with an HTML tag or modern JNLP applets do require the plugin.

Web Start applications (JWS), which are deployed using JNLP but run outside of the browser, do not require the plug-in.  They are usually launched using mime type associations to fire up javaws.  There is one mechanism that can be used to launch Web Start applications automatically using a JS call but that depends on the native Deployment Toolkit plugin, so if Google proceeds with their plans and if Oracle does nothing that would also be affected.

In both JNLP and tag-style applets, and JWS apps the deployment code takes care of downloading the application artifacts (JARs, DLLs, etc), both initially and if they have changed from what is in the Java app cache (e.g. javaws -viewer).


On Sep 29, 2013, at 6:17 AM, Mark Fortner <phidias51 at gmail.com> wrote:

> <snip>
> When you click a JNLP link (or button, invoke javascript, whatever...) the
> browser downloads a JNLP file then runs javaws to open that file. Beyond
> that there is no involvement with the browser.
> </snip>

> 
> I believe that's true for webstart applications, but not for webstart
> applets. In the latter case, webstart is used to handle jar caching and
> updating. And in that case, I believe applet startup would be effected.
> 
> Cheers,
> 
> Mark