trundler / existdb-webstart Goto Github PK

from @rvdb

I've given your webstart-0.1.xar a go, and in eXist's embedded Jetty context, I'm getting the same error as reported by @wolfgang:

"java.io.IOException: JNLP Jar download failure"

I've also checked in a Tomcat context and at first thought I was getting more sensible errors:

"com.sun.deploy.net.FailedDownloadException: Unable to load resource: http://localhost:8088/exist-3.5.0/rest/db/apps/webstart/jnlp.xq"

I've checked, and the resource mentioned /is/ available in a web browser. Closer investigaton revealed that the element in the generated index.jnlp file in the Tomcat context has:
codebase="http://localhost:8088/eXist-3.5.0/rest/db/apps/webstart/" href="jnlp.xq"
...while the one in eXist's embedded Jetty context has:
codebase="http://localhost:8080/exist/apps/webstart/" href="index.jnlp"

I've tried changing these values in the downladed index.jnlp from the Tomcat context to:
codebase="http://localhost:8088/eXist-3.5.0/apps/webstart/" href="jnlp.xq"
i.e. without the "/rest" prefix, and that works, in so far that I'm getting the same JAR download failure as in the embedded Jetty context :-/.

Perhaps the direct access via "/rest/" is bypassing the controller.xql and hence processing the "index.jnlp" path correctly? I've checked, and WEB-INF/web.xml does allow REST access ("hidden=false"). So, not to complicate the issue, but perhaps the $codebase variable in jnlp.xq needs to strip the "/rest/db/" part for portability?

• jnlp
• jars

• write build howto
• add references to quircks in macOS
• add some screenshots for webstart settings