JNLP links

[Greg Brown <gk...@mac.com>]

One thing I don't understand is why the JNLP links have to be  
absolute. Sandro, can you explain that part? Is it required by the  
Java Deployment Toolkit?

In any case, since we can't actually deploy our JSP-based JNLP files  
to our project site, why don't we just keep index.jsp and index.html  
separate. index.jsp can be used to launch Web Start versions, and  
index.html can be used to launch the applets.

G

Re: JNLP links

[Greg Brown <gk...@mac.com>]

>> Why don't we just rename index.jsp to web_start.jsp (or  
>> web_start.html,
>> since you are now using JavaScript instead of JSP)?
> Ok, but then in the webapp will be searched index.* , or a directory
> listing will appear (and it's not the best to change this setting in
> the web.xml).

No, index.html will still be there, so it will be found.

Re: JNLP links

[Greg Brown <gk...@mac.com>]

> 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) ?

Yes, I think this is a good idea.

>> 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.

I don't follow this. The only file we should need to manually modify  
during deployment (not WAR generation) should be kitchen_sink.jnlp.  
Everything else should stay 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 ?

Sure, if you prefer the JSP version.

Re: JNLP links

[Sandro Martini <sa...@gmail.com>]

> 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

Re: JNLP links

[Greg Brown <gk...@mac.com>]

> All this because I think it's important for us to show that we are Web
> Start compatible, form Site demos.

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).

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. 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.

Re: JNLP links

[Sandro Martini <sa...@gmail.com>]

Mhh another idea on this:
and keeping only the index.html (with new Javascript logic to get the
current url and split and pass to deploy) so at page side we have only
1 ... and maybe provide some static jnlp files with all path fixed
inside (the url of the site is always the same) ... and those files
maybe saved in our repository but in a site-dedicated subproject (and
loaded by hand into the site when needed), Ok ?

I don't like to duplicate things, but my previous idea seems less
practical, or could generate confusion.

All this because I think it's important for us to show that we are Web
Start compatible, form Site demos.


What do you think ?

Bye

Re: JNLP links

[Sandro Martini <sa...@gmail.com>]

> Why don't we just rename index.jsp to web_start.jsp (or web_start.html,
> since you are now using JavaScript instead of JSP)?
Ok, but then in the webapp will be searched index.* , or a directory
listing will appear (and it's not the best to change this setting in
the web.xml).

Probably in this case we could not copy *.jsp and *.jnlp in the task
for the web site, and instead copy all of them only in the war demos
task, maybe renaming web_start.jsp to index.jsp in the copy, and
removing other index.* from there, Ok ?

Sandro

Re: JNLP links

[Greg Brown <gk...@mac.com>]

> One last thing to note:
>
>> In any case, since we can't actually deploy our JSP-based JNLP  
>> files to our project site, why don't we just keep index.jsp and  
>> index.html separate. index.jsp can be used to launch Web Start  
>> versions, and index.html can be used to launch the applets.
> OK, but attention: index.html has priority over index.jsp so at least
> we have to copy inside war only the one that interests, and the same
> also for our site (to avoid confusion, also if jsp there isn't
> allowed).

Why don't we just rename index.jsp to web_start.jsp (or  
web_start.html, since you are now using JavaScript instead of JSP)?

Re: JNLP links

[Sandro Martini <sa...@gmail.com>]

One last thing to note:

> In any case, since we can't actually deploy our JSP-based JNLP files to our project site, why don't we just keep index.jsp and index.html separate. index.jsp can be used to launch Web Start versions, and index.html can be used to launch the applets.
OK, but attention: index.html has priority over index.jsp so at least
we have to copy inside war only the one that interests, and the same
also for our site (to avoid confusion, also if jsp there isn't
allowed).

Bye

Re: JNLP links

[Sandro Martini <sa...@gmail.com>]

Before I used the manual way, like Todd (standard links), but for
better consistency with the rest of our pages here I've used the
deployment toolkit and probably it has problems with relative links
... or, more in detail, giving to it a relative url and then pressing
the button, all seems to work but then i got a Web Start Error telling
that the jnlp file is not found ...

Byeeee

Re: JNLP links

[Todd Volkert <tv...@gmail.com>]

Ah - yeah, I just use standard <a href="foo.jnlp">...</a> - I use the
deployment toolkit on the page to make sure the user has the proper JRE
installed (if they don't, they'll get prompted to install Java immediately
when the page loads).

-T

On Fri, Oct 16, 2009 at 11:24 AM, Greg Brown <gk...@mac.com> wrote:

> Do you use the Java Deployment Toolkit to launch them, or are they just
> standard HTML anchor tags? I'm guessing that the absolute URL requirement
> comes from the deployment toolkit...
>
>
> On Oct 16, 2009, at 11:21 AM, Todd Volkert wrote:
>
>  FYI, I use relative jnlp links on my site that has deployed two live Pivot
>> apps, and they work.
>>
>> -T
>>
>> On Fri, Oct 16, 2009 at 11:13 AM, Greg Brown <gk...@mac.com> wrote:
>>
>>  One thing I don't understand is why the JNLP links have to be absolute.
>>> Sandro, can you explain that part? Is it required by the Java Deployment
>>> Toolkit?
>>>
>>> In any case, since we can't actually deploy our JSP-based JNLP files to
>>> our
>>> project site, why don't we just keep index.jsp and index.html separate.
>>> index.jsp can be used to launch Web Start versions, and index.html can be
>>> used to launch the applets.
>>>
>>> G
>>>
>>>
>>>
>

Re: JNLP links

[Greg Brown <gk...@mac.com>]

Do you use the Java Deployment Toolkit to launch them, or are they  
just standard HTML anchor tags? I'm guessing that the absolute URL  
requirement comes from the deployment toolkit...

On Oct 16, 2009, at 11:21 AM, Todd Volkert wrote:

> FYI, I use relative jnlp links on my site that has deployed two live  
> Pivot
> apps, and they work.
>
> -T
>
> On Fri, Oct 16, 2009 at 11:13 AM, Greg Brown <gk...@mac.com> wrote:
>
>> One thing I don't understand is why the JNLP links have to be  
>> absolute.
>> Sandro, can you explain that part? Is it required by the Java  
>> Deployment
>> Toolkit?
>>
>> In any case, since we can't actually deploy our JSP-based JNLP  
>> files to our
>> project site, why don't we just keep index.jsp and index.html  
>> separate.
>> index.jsp can be used to launch Web Start versions, and index.html  
>> can be
>> used to launch the applets.
>>
>> G
>>
>>

Re: JNLP links

[Todd Volkert <tv...@gmail.com>]

FYI, I use relative jnlp links on my site that has deployed two live Pivot
apps, and they work.

-T

On Fri, Oct 16, 2009 at 11:13 AM, Greg Brown <gk...@mac.com> wrote:

> One thing I don't understand is why the JNLP links have to be absolute.
> Sandro, can you explain that part? Is it required by the Java Deployment
> Toolkit?
>
> In any case, since we can't actually deploy our JSP-based JNLP files to our
> project site, why don't we just keep index.jsp and index.html separate.
> index.jsp can be used to launch Web Start versions, and index.html can be
> used to launch the applets.
>
> G
>
>