> I got this exception:
>
> CouldNotLoadArgumentException[ Could not load file/URL specified:
> /var/tmp/javawsZcVRT4]
>        at com.sun.javaws.Main.launchApp(Main.java:327)
>        at com.sun.javaws.Main.continueInSecureThread(Main.java:252)
>        at com.sun.javaws.Main$1.run(Main.java:111)
>        at java.lang.Thread.run(Thread.java:637)
>
> However, I was able to resolve it by enabling application caching in my Java
> Preferences.
Uh, I have no idea of why you have this problem ... are you on Mac ?

> How about this, then?
>
> <%
> String codebase = request.getScheme() + "://" + request.getServerName()
>    + ":" + request.getServerPort() + request.getContextPath();
> String href = request.getServletPath();
> %>
>
> This is also more efficient than parsing the string yourself (since the
> HttpServlet has already done that work for you).
Yes, you have reason :-) ... anyway I'm thinking to refactor some of
the common code from this page in one or more fragments, to reuse them
by including in other pages ...

>>> 2) We might want to consider mapping the "jnlp" extension to the JSP
>>> servlet
>>> so we can just call this file "kitchen_sink.jnlp".
>>
>> One question: changing the Application Server I could not be able to
>> run jsp pages (I could have no more Tomcat JSP classes available), it
>> is Ok ?
>> So I don't like too much this, but i can try to do the trick.
>
> This shouldn't require making changes to the application server - mapping an
> extension to a servlet is done in web.xml, as I recall.
Ok, but I fear if i have to map this extension to a Servlet (the JSP
Compiler) that could not exist on others applications server ...


> The Java Deployment Toolkit is working well for applets so far, so let's hold 
> off on JNLP applets for now.
Ok, don't worry.


Then I'll try to use the signed version of jars, to ensure that
Clipboard and custom files loading (etc)  goes right ... and if all is
working maybe we could write a note on this, in some page of
tutorials.

I've added also in the jnlp file the property that enables the
automatic ability to try to load pack.gz version of jars, but with Ant
this task is not integrated (and also with maven this is supported
only by some external plugin :-( ), but I'd keep that property, could
be useful for others ...


And later a last optimization:
I'd like to try also if make a standard jnlp file for all (runtimes,
without web, demos, tutorials, obsidian) Pivot jars, and reference it
as jnlp extension, but I have to do more tests on it ... could help to
have more modular (and simpler) jnlp files.


Thanks,
Sandro

Reply via email to