The Microsoft development environment deployment feature performs all required HTML updates to deployed HTML that references deployed Java classes so that changing the location of the file, through deployment, will not break the HTML link. Only the deployed HTML is updated on the Web server, not the HTML code saved in your project.
When considering deployed HTML, you should understand:
You can create HTML that references a Java class, such as a Java class behind HTML or a Java applet hosted on an HTML page. When you deploy this HTML reference tag and classes to a Web server, the Microsoft development environment will modify any <APPLET> or <OBJECT> tags in the deployed HTML to ensure that they reference the deployed classes in the correct location.
The deployment feature will add a CODEBASE parameter to all <APPLET> and <OBJECT> tags that reference deployed Java classes. The CODEBASE parameter will specify the deployed location of the Java class. This ensures that the deployed HTML is always able to access the deployed Java classes.
You can also create cabinet files and Zip files that contain Java classes. When you deploy cabinet or Zip files that contain Java class files and HTML files that reference those classes, the Microsoft development environment will modify any <APPLET> or <OBJECT> tags in the deployed HTML to ensure that they reference the deployed cabinet or Zip files in the correct location.
The deployment feature will add an ARCHIVE parameter to all <APPLET> tags that reference Java classes that have been deployed in a Zip file. The ARCHIVE parameter specifies the deployed location of the Zip file.
The deployment feature in the development environment will add a CABBASE parameter to all <APPLET> and <OBJECT> tags that reference Java classes that have been deployed in a cabinet file. The CABBASE parameter specifies the deployed location of the cabinet file.
Deploying will also add a set of USESLIBRARY parameters (in place of the CABBASE parameter) to all <APPLET> and <OBJECT> tags that reference for Java packages (as opposed to Java classes) that have been deployed in a cabinet file. The USESLIBRARY parameters specify the deployed location of the cabinet file, and the version and friendly name so that the Java packages in the cabinet file can be installed into the Java Package Manager.