This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
Is there any good method to test the JNLP application deployed in an application server?
Currently our team use "abbot" to test the swing application and it works fine, but the swing application is going to deployed through JNLP in application server and we want to find some good methods to test if the deployment environment configuration is okay or not. Any good sugguestion for that?
I haven't written JNLP files myself, but would it be possible to just fetch the JNLP file programmatically over HTTP, parse (and validate?) the file, and check that all the server-side resources referenced in the JNLP file are actually available?
Thanks for your suggestion but I think that your approach may not be able to verify the correctness of the jnlp application as it cannot check if all of the dependencies have been included and stated correctly or the application can be run by the web start.
It would be the best to test the application using abbot just as like running as a simple swing application, however after searching through the web, not a solution can be found for help.
Or any idea to test a JNLP application in an automatic and general way rather than by hands?
(sorry that I have repeated the same post in the other forum)
Joined: Jan 23, 2002
Hmm. How about including some kind of self-diagnostics tests into the Webstart application itself? Something that could be run with a shortcut under the "Help" menu, for example?