openjnlp-devel

[Openjnlp-devel] Questions about OpenJNLP

[scott p. <sco...@va...>]

Hello,

1. Does OpenJNLP support the "execution" of JNLP files from a GUI-less
machine (no Xserver for instance)?
2. Is there a way to stop a running application vis OpenJNLP once it has
been started?
3. How far along is the development process?

Thanks!

I have a middle-ware JINI application (set of services) I need to have
installed. JWS has some drawbacks in that it requires a GUI environment and
also has no way of stopping an application started with it (except using
kill -9)! Other than that, it is perfect for my needs. I hope this open
source project provides a good alternative. Thanks.

----------------------
Scott Pennell
Valaran Corporation
609-945-7260
http://www.valaran.com

"This communication may include the proprietary and confidential information
of Valaran Corporation.  If you believe you have received this communication
in error, please delete all copies and notify the sender by replying to this
e-mail."

Re: [Openjnlp-devel] Questions about OpenJNLP

[Christopher H. <he...@ez...>]

On Wednesday 20 February 2002 10:11, scott pennell wrote:
> Hello,
>
> 1. Does OpenJNLP support the "execution" of JNLP files from a GUI-less
> machine (no Xserver for instance)?
> 2. Is there a way to stop a running application vis OpenJNLP once it has
> been started?
> 3. How far along is the development process?
>
> Thanks!
>
> I have a middle-ware JINI application (set of services) I need to have
> installed. JWS has some drawbacks in that it requires a GUI environment and
> also has no way of stopping an application started with it (except using
> kill -9)! Other than that, it is perfect for my needs. I hope this open
> source project provides a good alternative. Thanks.
>

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.

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 
app starts spawning other JVMs and/or processes, that could be a problem); 
that doesn't mean it actually is easy.

3) Wellllll  Kevin Herr is the most consistent developer.  I've been working 
on it in fits and starts over the past few weeks, and have started folding 
our local work back into the main code base.  Kevin has been thinking more
strategically than I have (I concentrate mainly on "what do we need right now 
here at my company"), and is probably the better person to answer where 
OpenJNLP is going.

					Chris

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.

RE: [Openjnlp-devel] Questions about OpenJNLP

[scott p. <sco...@va...>]

Thanks Kevin and Christopher for responding. I will take a much closer look
now.

Scott

-----Original Message-----
From: ope...@li...
[mailto:ope...@li...]On Behalf Of Kevin
Herrboldt
Sent: Sunday, February 24, 2002 11:39 PM
To: ope...@li...
Subject: Re: [Openjnlp-devel] Questions about OpenJNLP


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.


_______________________________________________
Openjnlp-devel mailing list
Ope...@li...
https://lists.sourceforge.net/lists/listinfo/openjnlp-devel