Sorry I didn't notice this post until now.
The Sun app server, starting with release 9.0 (which is based on the GlassFish open source app server project at http://glassfish.dev.java.net) , provides automatic support for launching app clients using Java Web Start. Here's a link to a blog entry that describes how to use this feature: http://blogs.sun.com/quinn/entry/launch_app_clients_using_java
If the JNLP that is generated does not meet all your needs, then you will need to create your own JNLP. You can see the JNLP that is generated and you might be able to create your own based on that. It's not a good solution and we plan to make it possible for developers to specify much more of the generated JNLP in the next release.
- Tim
Thx for your reply.
Actually I have already customized my app with these features.
It could be nice if i was possible:
- to specified an image file (in my jar), to be used as splash screen.
- to provide an image icon to be used in program shortcut.
- to set some java web start options in my deployment descriptor, such as, installing shortcut at deployement time, silent download for application launch other than the very first launching.
- to disable "JAVA STARTING" splash screen.
To make this short, do you think, it will be possible to use JWS full features to deploy a trusted (or not) javaee client application ?
thx guys for being there
Ghislain N.
..
> It could be nice if i was possible:
> - to specified an image file (in my jar), to be used
> as splash screen.
Java 6 offers the ability to include a splash
image in an application jar file, but that clashes
with the webstart approach of putting the splash
image separate to the application jar files, and
specifying it in the JNLP launch descriptor.
> - to provide an image icon to be used in program
> shortcut.
That can be configured in the JNLP file,
though some *nix systems do not use the
icon.
> - to set some java web start options in my deployment
> descriptor, such as, installing shortcut at
> deployement time,
Options in the JNLP can be used to offer
a shortcut to the end user. Whether they accept
an icon, is up to them.
>..silent download for application
> launch other than the very first launching.
> - to disable "JAVA STARTING" splash screen.
Why? What does that offer to the end user?
Basically, the splash screen is for the benefit
of the end user, and if Sun were to offer* the
ability to suppress it, it would be probably be
done at the level of the Java Control Panel (JCP).
But then, if I saw an option in the JCP to
|_| Show a splash when downloading new
program resources or
|x| Simply show a 'blank screen' between when
I double click the shortcut, and ten seconds later
when the application appears.
I would almost certainly ask for the 'splash'
since the second makes no sense at all.
* As such, I doubt Sun will be offering to suppress
that, even through the JCP.
> Java 6 offers the ability to include a splash
> image in an application jar file, but that clashes
> with the webstart approach of putting the splash
> image separate to the application jar files, and
> specifying it in the JNLP launch descriptor.
Yes in a standalone java application, but not in a javaee client application deployed from Sun AS9 with JWS enabled.
> That can be configured in the JNLP file,
> though some *nix systems do not use the
> icon.
>
> Options in the JNLP can be used to offer
> a shortcut to the end user. Whether they accept
> an icon, is up to them.
>
the JNLP file is not configurable!
> Why? What does that offer to the end user?
> Basically, the splash screen is for the benefit
> of the end user, and if Sun were to offer* the
> ability to suppress it, it would be probably be
> done at the level of the Java Control Panel (JCP).
Do you ever have to go to control panel, to choose to install shortcut of an application you already choose to install on your system?
I just think, they choose the wrong default option. But that not the point.
Shortcut should at least be installed in programs menu. Desktop shortcut should be approved by end user.
>
> But then, if I saw an option in the JCP to
> |_| Show a splash when downloading new
>program resources or
> | Simply show a 'blank screen' between when
>I double click the shortcut, and ten seconds later
> when the application appears.
> I would almost certainly ask for the 'splash'
> since the second makes no sense at all.
>
> * As such, I doubt Sun will be offering to suppress
> that, even through the JCP.
Last point:
End users are interested in the application they are installing. They don't need to know what java is doing behind the scene. Most user react, on JAVA STARTING splash "Is this your application ?".
A few quick notes on this...
> the JNLP file is not configurable!
In response to requests filed as GlassFish issues the latest promoted build of GlassFish allows the developer to specify his or her own splash and/or icon images. See this blog entry
http://blogs.sun.com/quinn/entry/specifying_icon_and_splash_images
that describes how. It's not the cleanest solution, I'll agree. We hope to permit much more extensive customization of the generated JNLP in a future release but this was a low-impact way of letting developers specify images now.
As for suppressing certain information, look in the Java Web Start forum for topics along these lines. Also the javaws command documentation
http://java.sun.com/javase/6/docs/technotes/tools/share/javaws.html
describes the -Xnosplash option. It is not the automatic mechanism you described but it is there.