Known issues

FAQ Answers

What JNLP functionality does Ant Web Start Task lack?

Ant Web Start Task is meant to be a quick and easy way to get an application distributed via webstart; in striving for simplicity, it also loses some of the power offered by the full JNLP spec. Some of these shortcomings are: Let us know if there's any we've missed.

What future developments are planned for the Ant Web Start Task?

Fix all known issues, which are: Let us know you think you can help in any way.

Why doesn't my application work with Java<1.5 or Mac OSX<10.4?

Some of the elements supported by the Ant Web Start Task were made available in the JNLP specification v1.5. This spec is implemented by Java v1.5; as a result, older Web Start clients (including the one shipped with OSX<10.4) will not be able to launch the application if it contains elements which are defined in the newer JNLP v1.5 spec. The workaround is to not use any of these elements in your task definition - the elements that are new to the JNLP v1.5 spec are clearly marked in the task definition.

In future versions of the Ant Web Start Task, it may be possible to autodetect which version of Java is installed on the client browser, although because this would be javascript-based it would not be guaranteed to work perfectly cross-platform.

How does versioning work in the Ant Web Start Task?

One of the main advantages of Java Web Start is the ability to version jar files, allowing users to only download thoses jars that have changed. Versioning support in the Ant Web Start Task is pretty minimal; the original timestamp of the jar file is preserved in the WAR archive, which means that the client Web Start deployer will decide whether a user's jars need updating based on its timestamp. This is not very convenient for multi-developer environments where more than one developer can create and deploy the WAR archive.

Moreover, the Ant Web Start Task does not keep older versions of updated jars, and so jar-diffing is not supported. There are no plans to support this in the future; this kind of functionality is difficult to achieve as part of the build process. If you need this kind of functionality, it would be easiest to roll out a custom JNLP file and application archive and maintain them manually.

How does the Ant Web Start Task decide which version of the JNLP spec to use?

New elements have been added to the JNLP specification with J2SE 1.5 - a JNLP file with version 1.5 is not parseable by a previous version of the Web Start client. At the moment the spec number tends to go to 1.5 more often than it needs to; this should be fixed, and a warning should be issued if the user selects an elements that are 1.5+ specific.