The URLs used for the Java Web Start support do not correspond directly to directory structures named the same way on the server. This is to prevent malicious users from using the Java Web Start support to browse the server's directory structure. So it's not surprising that you didn't find directories named in parallel with the URL path or that creating them yourself didn't help; the server is not looking there for the file(s) but maps the paths to the correct on-disk locations.
The <install-dir>/domains/domain1/java-web-start/appserv-jwsacc.jar location is where the server will look for the file. That is a signed version of the same-named JAR that is in the <install-dir>/lib directory.
I have just tried a simple experiment on a Mac with java SE 1.6.0_07 and the Java Web Start support worked fine, so it does seem to be something in your environment that is not quite right.
You can try using the admin console to turn on FINE-level logging for the deployment logger. Then try accessing the URL again and see if the server reports anything useful.
- Tim
[Message sent by forum member 'tjquinn' (tjquinn)]
http://forums.java.net/jive/thread.jspa?messageID=330407