I'm having trouble passing arguments to a Java application started using Java Web Start. My system is Ubuntu Linux 12.04.1 Precise, but the same also happens in Windows 7. Both use Oracle Java version 1.7.0_09.
Edit: I'm investigating if a Web Start application would suit our needs better than a normal applet. The problem with an applet is that it gets closed if the user navigates away from the page which is not what we want. (We're also interested in seeing if we can get around a certain security issue by using Web Start instead of an applet.) We'd like to start the application from the browser so that we could pass information about the authenticated user to the Java application. Requiring the user to login in the application seems like a bad solution (we might have to support things like OAuth).
I have a sample program CommandLineArgs.java:
public class CommandLineArgs {
public static void main(String[] args) {
System.out.println(String.format("Got %d command line args:", args.length));
for (String arg : args) {
System.out.println(arg);
}
}
}
I packaged this into a jar:
javac CommandLineArgs.java
zip cmd.jar CommandLineArgs.class
Then I have a JNLP file called cmd.jnlp:
<?xml version="1.0" encoding="utf-8"?>
<!-- Empty codebase means use same directory. -->
<jnlp spec="1.0+" codebase="https://localhost:9876/">
<information>
<title>Command Line Args Printer</title>
<vendor>No one</vendor>
<homepage href="https://localhost:9876/"/>
<description>Application that prints the command line arguments that it gets.</description>
</information>
<resources>
<j2se version="1.6+" initial-heap-size="32m" max-heap-size="128m" />
<property name="jnlp.versionEnabled" value="true"/>
<jar href="cmd.jar" main="true"/>
</resources>
<application-desc main-class="CommandLineArgs">
<!-- Here are sample arguments I'd like to pass to the program. -->
<argument>arg1</argument>
<argument>arg2</argument>
<argument>arg3</argument>
</application-desc>
</jnlp>
Here's a HTML page cmd.html I use for testing. The div element was originally created by using deployjava.js: deployJava.launchWebStartApplication('https://localhost:9876/cmd.jnlp')
<!DOCTYPE html>
<html>
<head>
<title>Java web start command line arguments test</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
</head>
<body>
<div id="div1" style="position: relative; left: -10000px; margin: 0px auto; " class="dynamicDiv">
<embed type="application/x-java-applet;jpi-version=1.7.0_09" width="0" height="0" launchjnlp="https://localhost:9876/cmd.jnlp" docbase="https://localhost:9876/">
</div>
</body>
</html>
The fastest way I could get a https server running was to use the openssl tool commonly found in Linuxes. When running the server like this, the current directory should contain cmd.html, cmd.jar and cmd.jnlp .
sudo cp /etc/ssl/private/ssl-cert-snakeoil.key .
sudo chmod 666 ssl-cert-snakeoil.key
openssl req -batch -new -x509 -key ssl-cert-snakeoil.key -out ssl-cert-snakeoil.key.crt
openssl s_server -cert ssl-cert-snakeoil.key.crt -key ssl-cert-snakeoil.key -accept 9876 -WWW
Now if I surf to https://localhost:9876/cmd.html I can run the application. The Java console opens and it prints this. Notice that there are 0 command line arguments.
JNLP Ref (absolute): https://localhost:9876/cmd.jnlp
Match: beginTraversal
Match: digest selected JREDesc: JREDesc[version 1.6+, heap=33554432-134217728, args=null, href=null, sel=false, null, null], JREInfo: JREInfo for index 0:
platform is: 1.7
product is: 1.7.0_09
location is: http://java.sun.com/products/autodl/j2se
path is: /opt/jre1.7.0_09/bin/java
args is: -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8001
native platform is: Linux, amd64 [ x86_64, 64bit ]
JavaFX runtime is: JavaFX 2.2.3 found at /opt/jre1.7.0_09/
enabled is: true
registered is: true
system is: true
Match: ignoring maxHeap: 134217728
Match: selecting InitHeap: 33554432
Match: digesting vmargs: null
Match: digested vmargs: [JVMParameters: isSecure: true, args: ]
Match: JVM args after accumulation: [JVMParameters: isSecure: true, args: ]
Match: digest LaunchDesc: null
Match: digest properties: []
Match: JVM args: [JVMParameters: isSecure: true, args: ]
Match: endTraversal ..
Match: JVM args final: -Xms32m
Match: Running JREInfo Version match: 1.7.0.09 == 1.7.0.09
Match: Running JVM args match: have:<-Xms32m satisfy want:<-Xms32m>
Got 0 command line args:
On the other hand, if I run javaws from the command line (javaws cmd.jnlp), I get this in the java console. Now there are 3 command line arguments.
Match: beginTraversal
Match: digest selected JREDesc: JREDesc[version 1.6+, heap=33554432-134217728, args=null, href=null, sel=false, null, null], JREInfo: JREInfo for index 0:
platform is: 1.7
product is: 1.7.0_09
location is: http://java.sun.com/products/autodl/j2se
path is: /opt/jre1.7.0_09/bin/java
args is: -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8001
native platform is: Linux, amd64 [ x86_64, 64bit ]
JavaFX runtime is: JavaFX 2.2.3 found at /opt/jre1.7.0_09/
enabled is: true
registered is: true
system is: true
Match: ignoring maxHeap: 134217728
Match: selecting InitHeap: 33554432
Match: digesting vmargs: null
Match: digested vmargs: [JVMParameters: isSecure: true, args: ]
Match: JVM args after accumulation: [JVMParameters: isSecure: true, args: ]
Match: digest LaunchDesc: null
Match: digest properties: []
Match: JVM args: [JVMParameters: isSecure: true, args: ]
Match: endTraversal ..
Match: JVM args final: -Xms32m
Match: Running JREInfo Version match: 1.7.0.09 == 1.7.0.09
Match: Running JVM args match: have:<-Djnlp.versionEnabled=true -Xms32m satisfy want:<-Xms32m>
Got 3 command line args:
arg1
arg2
arg3
Am I doing something wrong? Why don't the arguments get passed to my program when running in the browser?
I found the post Java WS application ignoring arguments sporadically that seems to describe the same problem. The solution for posdef was to remove the href attribute from the jnlp element in the jnlp file but I don't have that attribute.
The security environment applied to JWS based apps. was always very similar to that applied to applets. Some minor differences were that
System.exit(n)was always restricted in applets (even trusted ones) and that JWS offered an intermediate level of security between sand-boxed and trusted.Sun went to great effort to integrate the two forms of the plug-in before Oracle bought them.
So the short answer to that ..question is, 'no'. If you can do it in a JWS app., you should be able to do it in an applet.