Use to configure your application so that the application can be deployed using Java Web Start. Java Web Start enables users of your application to download and launch the application by clicking a link in a web browser.
The Web Start page has the following properties, which are used in the creation of the JNLP file. The JNLP file is used to launch the application.
Element | Description |
---|---|
Enable Web Start |
Creates the necessary artifacts to make the application deployable with Java Web Start when you build the application. These artifacts can be found in the application's dist folder. |
Icon |
Specifies the icon to be used to represent the application on the user's system, such as on the desktop. |
Codebase |
Specifies a URL representing the location of the application.
This field is a represented by a combo box from which you can select Local Execution, Web Deployment, or User Defined. For Local Execution and Web Deployment, the URL is determined automatically for you. If you select Web Deployment, |
Allow Offline |
Enables the user to run the application without a network connection. |
Extension Resources |
Specifies dependencies on the JNLP files of additional resources (APIs, libraries, or system properties) that should be used as part of your application when it loads through Java Web Start.
To specify an extension resource, enter the following attributes: Href, Name, and Version. |
Href |
Specifies a URL to a JNLP file of the resource you want to add. For example, http://somesite.org/mylib.jnlp |
Name |
(Optional) Specifies an arbitrary name of the extension resource. |
Version |
(Optional) Specifies a version of the extension resource. |
Self-signed |
Signs the application using a certificate that is generated when the project is built.
This certificate is not certified by any Certification Authority. Self-signing an application enables the application to do things such as write files to disk and access the network. If you select the Self-signed option, choose one of the following options that determine how to handle the signed and unsigned components in your Java Web Start applications and applets: Enable Software Protections, Trusted Only, or Trusted Library. |
Enable Software Protections |
Displays a warning dialog box during loading of your Java Web Start application with mixed components (signed and unsigned). |
Trusted Only |
Does not display a warning dialog and an application or applet that loads a jar file containing this attribute does not load any untrusted classes or resources. This measure prevents a signed application or applet from being re-purposed with unsigned components.
Use this attribute for applications and applets that do not require unsigned components. All classes and resources in the application or applet must be signed. |
Trusted Library |
Allows unsigned components to be mixed with signed components (for example, signed libraries) without a warning dialog being displayed.
All classes and resources in a JAR file containing this manifest attribute must be signed. Trusted library code is loaded into a separate dedicated class loader which is unique to the application or applet. This ensures that the trusted library code cannot be replaced. |
Application Descriptor |
Generates the JNLP file with the application-desc element.
The |
Applet Descriptor |
Generates the JNLP file with the applet-desc element.
The |
Component Descriptor |
Allows the project to be called as a resource from the JNLP file of another application. |
Related Topics
Developing Applications with NetBeans IDE,
Developing Applications with NetBeans IDE,
Developing Applications with NetBeans IDE,
Copyright © 2016, Oracle and/or its affiliates. All rights reserved. |