Philippe Nobili wrote: > > We have used the Web deployment facilities provided by XMLMind 4.4; it's > really a great feature which will allow us to bridge the gap between our > CMS, the source management tools and XML authoring with XMLMind. We have > one suggestion for improvement: > > (Note: it might well be that we could not find the way to do this with > the deploywebstart script) > > Usually, we want to deploy different "flavors" of XMLMind on the Web, > because of the different possible contexts of use, but we want to keep > only one set of signed JAR files for all these different deployment > flavors. > > We cannot currently run deploywebstart several times (for the Java Web > Start deployement and for the different possible applets) because the > JNLP and index files all have the same name. So, we have do this > manually, keeping only one set of signed JAR files and editing and > moving around index.html and JNLP files by hand. > > It works, but maybe a simple modification in deploywebstart script would > do the job automatically ? For example: (Just for illustrating the > suggestion) > > % ./deploywebstart -webstart -applet viewer -applet editor2 -applet xxe > > Would create in directory "webstart" the files: "webstart.html", > "webstart.jnlp", "viewer.html", "viewer.jnlp", "xxe.html", "xxe.jnlp", > etc etc > >
Thank you for your suggestion, which is a very reasonable one. However, the deploywebstart command-line tool is already too complicated and we currently do not intend to add even more complexity. We suggest to wrap this command-line tool in your own script: invoke deploywebstart once then use sed (or an XSLT style sheet) to generate variants of index.html and xxe.jnlp.
