Turned out to be a Web Start permissions issue. The <all-permissions/> tag
in the JNLP did not cover code contained within the .war file.
Adding the following to my jetty startup class made it work.
Policy.setPolicy(
new Policy() {
public PermissionCollection getPermissions(CodeSource
codesource) {
Permissions perms = new Permissions();
perms.add(new AllPermission());
return (perms);
}
public void refresh() {}
}
);
I didn't know it was permissions until I tried explicit context pathing in
web.xml (thanks, Matt.) I then got a more meaningful error about read
permissions. Once I added the above code, however, I was able to revert to
relative paths.
Another way might be to retrieve the .war via a jnlp resource locator. I
imagine if it is executed directly from the Web Start cache, instead of
throwing it to disk first, I bet it would also work.
mraible wrote:
>
> That's quite strange it doesn't work. What happens if you change the
> paths to be explicit instead of using wildcards?
>
> FWIW, Hudson has a Java Web Start demo that uses Jetty and allows you
> to view their full application - could be very cool for 1-click demos
> of AppFuse or AL.
>
> https://hudson.dev.java.net/hudson.jnlp
>
> Matt
>
>
--
View this message in context:
http://www.nabble.com/Embedded-Jetty-under-Java-Web-Start-tf4318480s2369.html#a12359010
Sent from the AppFuse - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
