On Apr 25, 2011, at 10:21 AM, Camaleón wrote: > On Sun, 24 Apr 2011 20:33:45 +0000, Liam O'Toole wrote: > >> On 2011-04-24, Camaleón wrote: > > (...) > >>>> Once the user "trusts" the application, the local JVM will load and >>>> run the JAR file exactly as if it had originally resided on the local >>>> hard drive. >>> >>> Yes, but not all java applications are ready to be used with that >>> method. If you can tell me a sample case, I will test :-) >> >> --- SNIP --- >> >> I cannot provide you with a sample case to prove a negative! Instead I >> invite you to download the sample .jnlp file in the link I provided >> earlier and modify it to suit your LAN. > > Okay, I just have tried to create a JNLP file to launch the JAR file that > is stored on a samba share but I'm still facing the same problem that we > are encountering from the beginning: "smb://" protocol is not detected ;-( > > If I place the "test.jnlp" file locally it can be run (it fails because > it looks for a signature file that seems to be missed from the original > jar but anyway it recognizes the JAR and tries to launch it), but when I > put the same "test.jnlp" file over a samba share and run the app from a > linux client it does not work "(java.io.FileNotFoundException: smb:/host/ > share/test.jnlp (No such file or directory)". > > Needless to say the same "test.jnlp" that is located on the network share > runs fine when it's launched from a windows client ;-(
I think this setup will solve both our problems. But don't try to launch it from a network share, set up Apache (or another web server) and launch it through there. I tried Liam's example from the command line and it works perfectly -- it just means we have to put the program in a directory where Apache can serve it, instead of sharing it through SMB or NFS. Hal -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
