Java Deployment Toolkit : Java Glossary
The OBJECT and EMBED tags
to invoke a Java Applet so ugly, so verbose, so impossible to maintain that with
JDK (Java Development Kit) 1.8.0_112, that Oracle came
OBJECT and EMBED tags not
being properly standardised. It is a recipe for flakiness and problems with
lesser-known browsers. The saving grace is the scheme will automatically install Java
if it is not already installed. I think that is just as easily and much more
reliably, handled with a Jump to Java button.
It consists of a deployJava.js script that you upload to
your website. Alternatively you can link it directly from Oracle’s website from
either http://www.java.com/js/deployJava.js or https://www.java.com/js/deployJava.js for embedding in secure pages. The
advantages of serving it locally include:
The advantages of serving it from Oracle include:
- Oracle cannot change the code for deployJava.js on you
without warning, which might cause your website to stop working properly.
- If your website is up, deployJava.js will be
available, independent of whether sun.com is
currently-installed JRE (Java Runtime Environment) versions, trigger the installation of the latest
an Applet tag, create a JWS (Java Web Start) launch button, etc.
- Oracle’s servers are larger and better cached.
- Your clients automatically get the latest Oracle code, including the latest bug
- Oracle recommends you do it this way.
Oracle’s Technote Guide on Deployment Advice