I am evaluating the possibilities of using JWS in a senario mentioned below, please guide me on this.
We have a Java Web Application (which requires tomcat, mysql) to be bundled in a CD along with the product developed by us. In this case whether JWS can used for packaging and deployment? thanks in advance Jayakrishnan
hi, if you are bundling your product on cd you will most likely have some installation manager that could install the java web app. it would be a bit of an overhead to let the user start the cd, then his/her browser, open a html site on the cd and start jws. the only benefit of the cd-jws-app would then be that the user does not need to download the java app over the internet. but using the cd as homesite for the jws app means that you will not be able to deploy any updates through this jws app, unless you provide a new jnlp file (which means, in fact, to provide a new jws app as JavaWebStart differences apps through homesite addresses). a "dirty" solution to provide an installation of a jws app without download but with the possibility to download updated over the internet would be: to install the app into the jws cache. but that is totally theoretical, I suppose, from my view of the jws cache. hope this was not too huddled together... if you have not installed a jws app yet, you should do it for testing purposes to see what its advantages and disadvantages are. Chantal