Hi, > Good catch. I have added "*.jsp" and "*.wtkx" to the "trim-whitespace" target. Ok, but for "*.wtkx" you means "*.wtk*" or "*.wtkd", I suppose ...
>>- in build.xml, html pages are as .template.html, and then copied as .html, >>Ok. >> For jsp pages I have to do the same, right ? > > The templates are used to make sure that the HTML files use the right Pivot > version (see the "@version@" tags in the *.template.html files). Now that I > think about it, it occurs to me that there might be a better alternative. We > could simply define one version.template.js file that is processed by the > build and use that to dynamically construct the JAR file names in JavaScript. > You could do something similar in JSP (e.g. version.template.jsp). Yes, but so we need another file to be generated by the build, or I could try to reuse the same version.template.js from my jsp ... And probably I could try to make only 1 jsp page for the Web Start execution, passing some parameters ... but i have to see if all tutorials / demos can work (good) with the same parameters (same width, height, etc) otherwise i have to pass all them to the jsp. For the Web Start execution, I like more the approach to add another link for any application from the index page, without having to enter in the page, load the Applet version and then load the Web Start version, ok ? >> And add jsp in some filter, like already done for jnlp, right ? > > Not sure what you mean by this. There are some tasks that copy template files with the right extension, so i think to do the same also for jsp pages, both for demos and tutorials ... >>- in README maybe we should add also the requirement that some pages >>are dynamic and requires JSP to work. I've used stripped version of >>Jetty without jsp for example, but this is not an usual configuration, >>so should not be a problem. > > I think the fact that we package these files into a WAR is probably > sufficient notice that a servlet container is required. Ok, I agree. Thanks, Sandro
