[GLASSFISH-1118] WebStart needs a way for user to influence JNLP generation (add native dll/so) Created: 08/Sep/06  Updated: 23/May/13  Resolved: 23/May/13

Status: Resolved
Project: glassfish
Component/s: standalone_client
Affects Version/s: 9.1pe
Fix Version/s: 3.1.2

Type: Improvement Priority: Critical
Reporter: phenderson Assignee: Tim Quinn
Resolution: Fixed Votes: 5
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: All
Platform: All

Issuezilla Id: 1,118


My swing gui client uses JDIC, which has some native libraries (.dll/lib*.so).

At present there is no means to specify additional libraries in

A possible solution:
List additional JNLP libraries (extensions) in sun-application-client.xml.
Although this could mean that the extension JNLP file would have to be modified
by Glasfish to reflect codebase changes. (JnlpDownloadServlet already does
something like this so perhaps use that)


Comment by Tim Quinn [ 21/Sep/06 ]

There are several ways we would like to make it possible for developers to
influence or add to the JNLP used for launching app clients. This is a good
concrete example of one of those requirements.

If and when we address this it probably will indeed involve changes to the sun-
application-client.xml descriptor. Because some of the settings we would like
to open up to the developer might need to be in the main JNLP that GlassFish
generates, we may need to do more than just allow the developer to specify
extension JNLP documents in the descriptor.

  • Tim
Comment by Tim Quinn [ 15/Feb/07 ]

I have modified the title of this issue to reflect the general desire to allow
developers to influence the generation of JNLP content.

Comment by Tim Quinn [ 15/Feb/07 ]
      • Issue 2397 has been marked as a duplicate of this issue. ***
Comment by Tom Mueller [ 06/Mar/12 ]

Bulk change to set fix version to "not determined" where the issue is open but the value is for a released version.

Comment by Tim Quinn [ 23/May/13 ]

This was resolved long ago. I finally noticed this bug.

Generated at Tue Feb 28 13:07:41 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.