The Application Client URL

The default URL for a stand-alone application client module
is as follows:

http://host:port/appclient-module-id

The default URL for an application client module embedded within
an application is as follows. Note that the relative path to the application
client JAR file is included.

http://host:port/application-id/appclient-path

If the context-root, appclient-module-id, or application-id is not
specified during deployment, the name of the JAR or EAR file without
the extension is used. If the application client module or application
is not in JAR or EAR file format, an appclient-module-id or application-id is generated.

You can also pass arguments to the ACC or to the application
client's main method as query parameters in
the URL. If multiple application client arguments are specified, they
are passed in the order specified.

A question mark separates the context root from the arguments.
Ampersands (&) separate the arguments and their
values. Each argument and each value must begin with arg=.
Here is an example URL with a -color argument for
a stand-alone application client. The -color argument
is passed to the application client's main method.

http://localhost:8080/testClient?arg=-color&arg=red

Note –

If you are using the javawsURL command to launch Java Web Start with a URL that contains
arguments, enclose the URL in double quotes (")
to avoid breaking the URL at the ampersand (&)
symbol.

Ideally, you should build your production application clients
with user-friendly interfaces that collect information which might
otherwise be gathered as command-line arguments. This minimizes the
degree to which users must customize the URLs that launch application
clients using Java Web Start. Command-line argument support is useful
in a development environment and for existing application clients
that depend on it.