There is now a couple more scripts on the Fix Webstart Page: http://confluence.concord.org/display/CCTR/WebStart+OSX+Java+1.5+Fix
These scripts allow technical users to fix their webstart on OSX 10.4 and 10.5. The latest Java update for 10.4 (1.5.0_13) changes the paths to webstart and it removed the 1.4 webstart. So there is now a script for that situation. The Java installed on Leopard 10.5 (1.5.0_13) also changes the paths to webstart and removed the 1.4 webstart. So there is a custom script for that. All of the scripts now download a zip file (using curl) from confluence and add its contents to the webstart file. The next step is to update the "Fix Webstart" application so it is easy for non technical users to apply the fix. Scott Scott Cytacki wrote: > Comments interspersed... > > Paul Burney wrote: > >> [EMAIL PROTECTED] >> <mailto:[EMAIL PROTECTED]> on November 20, 2007 at 17:13 >> wrote: >> *And if you want to test your webstart for the fix you can follow the >> directions here: >> http://www.telscenter.org/confluence/display/PAS/JNLP+Test >> >> If someone with 10.5 wants to verify the there is still a problem with >> webstart please let us know. >> >> OK. >> >> 1) I verified that the original problem persists: "Waiting for data..." >> >> > Ok. That is what I figured. > > >> 2) I verified that the Java Web Start fix program doesn't work on >> 10.5. It says: >> >> "Fix not applied. This fix only works with Java 1.5.0_06 and >> 1.5.0_07. You have version: 1.5.0_13. Please Quit this program now" >> >> I'm not sure if the actual files have changed or only that this script >> only is checking Java version numbers. >> > Yes I now have 10.5 so I checked, and the files have changed location. > I have not figured out yet if the old javaws.jar is even on the machine > anymore. I found jaws.jar in the java 1.4 folder but I think that is > something else. > > On 10.4 the javaws.jar was inside of the webstart application bundle. > There were 2 webstart app bundles one for 1.4 and one for 1.5. > > On 10.5 there is only one webstart app bundle, and it doesn't have the > javaws.jar. I opened the exe that app bundle is running (in text edit) > and found the classpath hard coded in there. It was pointing to: > > /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/javaws.jar > > > >> Would it be possible to just have a new launcher as the first download >> that looks for the fix from within Java and then applies it if >> necessary before calling the other JNLP? That way it's seamless for >> the OS X user because I doubt Apple will ever fix this bug. >> Additionally, you could probably do some other things like checking >> for proxy settings, network connections, permissions, etc., and try to >> fix those errors before the rest of the application starts up. >> > It is possible. We've been talking about that for a while now, > unfortunately there isn't a jira issue to record that conversation. The > biggest problem is permissions, many students don't have perms to modify > the file which needs to be modified. But at least identifying the > problem would be much better than just sitting there. > > Scott > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
