> I don't mind supporting one or two JNLP demos on the site for this reason,
> but I don't want to try to handle them all (because we will need to manually 
> modify every one).
Ok, I agree.

> I would suggest that index.html link to kitchen_sink.jnlp (via an anchor tag 
> with a relative link), and we can manually update kitchen_sink.jnlp when we 
> deploy to the site.
Ok, Monday I'll do it.
But to avoid questions from users like "I cannot paste text from the
clipboard", do you think is better to use the signed version (and not
use other 2 jnlp) ?

> All the other JNLP files can be linked to from web_start.html using whatever 
> means you think is best.
> We won't deploy web_start.html or any of the other JNLP files to the site.
Ok, we have only to remember to copy it as index.html/jsp during war generation.
If you think could simplify this process, i could also move all them
in a dedicated subdir so maybe the exclusion will be simpler ... maybe
Todd can tell us what he prefers here :-) , for me is the same.

So if things are in this way, maybe i could keep my index.jsp
(renaming it to web_start.jsp), and avoid write Javascript code to do
what I'm already doing in the current page, Ok ?


Thanks again, and now I have to go, really ...
Sandro

Reply via email to