First, for Peter.
Thanks for the feedback. I had accumulated many files in my temp directory and cleaning it out helped a great deal. (I got the idea after using the NetBeans profiler to see where the time was going. On the Windows system I was using a JDK class working with a secure random number seed was invoking java.io.File.list which took more than 13 seconds before I cleaned out the temp directory. (I had a LOT of files that had piled up there.)
And just to be clear, the directory of interest is the one pointed to by the java.io.tmpdir system property.
There may be other things going on in your case. Just out of curiosity, how many files resided in your temp directory before you cleaned it out?
Now for Steve,
Can you please use IssueTracker to open a GlassFish enhancement request for this? Java Web Start itself is in control of how long the splash screen stays visible. It might be possible for the app client container to display the splash screen again when it starts up.
Another additional enhancement could be for the app client container to call back to an optional developer-supplied class with progress updates. Then the developer could choose whether and how to inform the user of the start-up activities.
Of course the best of all would be if all the start-up activities happened so fast that neither of these steps was needed.
- Tim
[Message sent by forum member 'tjquinn' (tjquinn)]
http://forums.java.net/jive/thread.jspa?messageID=212909