Re: [Openjnlp-devel] Questions about OpenJNLP

[Kevin H. <ke...@na...>]

On Sunday, February 24, 2002, at 10:16 , Christopher Heiny wrote:
[...]
> 1) As far as I can tell, it should - if you pass it a jnlp file as an
> argument, it opens that file without opening the GUI.

All of the GUI-related code is in openjnlp-app.jar. If passing the URL 
as an argument doesn't work there, you can invoke OpenJNLP in non-GUI 
mode by passing the URL(s) as arguments using 
"org.nanode.jnlp.JNLPParser" as the main class.

> 2) Not that I know of, but it's a cool idea.  After 35 seconds 
> thought, I
> can't think of a reason why it wouldn't be fairly easy for most apps 
> (if the

Killing off running apps is an idea I've had for a while, although it's 
been rather low priority. Since the OpenJNLP launcher tracks all 
launched apps via the corresponding java.lang.Process object it should 
be possible to stop a running app. It's very abrupt and is not a good 
way to stop stuff but could be done.

> 3) Wellllll  Kevin Herr is the most consistent developer.  I've been 
> working

OpenJNLP is pretty far along, IMHO. It's quite functional as a JNLP 
client, supporting execution of the majority of JNLP apps written. Some 
plans for OpenJNLP are (in no particular order):

Updated 1.1 version
Required JNLP services
Optional JNLP services
Applet launching
Operating System integration (".jnlp" file mapping, allowing links in 
browsers to launch)
Cache management
Version-based updating
Security

The launching stuff was a major feature. Launching is pretty decent now 
although it needs improvement. Security is the next "big thing" that 
will take a major amount of effort.