|
Replies:
3
-
Last Post:
Dec 4, 2008 1:10 AM
by: mthornton
|
Threads:
[
Previous
|
Next
]
|
|
|
|
|
|
Webstart temp folder permissions problem a bug?
Posted:
Dec 3, 2008 4:48 AM
|
|
|
Webstart uses a temp folder to store the downloaded files.
This folder is often not writable for our customers/users of our program.
(e.g. A sysadmin installs java as administrator and the user can't write in the temp folder of the administrator off course)
This results in "failed to load application"
Can I consider this a bug in Javaws?
it should prompt the user to select a folder if javaws cannot write to its cache/temp folder.
to simply fail is not a good way to give confidence in our program.
|
|
|
|
|
|
|
Re: Webstart temp folder permissions problem a bug?
Posted:
Dec 3, 2008 7:28 AM
in response to: schaatser
|
|
|
On Windows, WebStart uses a per user temp directory which ought to be writable by that user unless the system is badly screwed up.
What operating system are you using and where is the temp folder concerned?
|
|
|
|
|
|
|
|
|
Re: Webstart temp folder permissions problem a bug?
Posted:
Dec 3, 2008 2:37 PM
in response to: mthornton
|
|
|
we deploy the webstart program, our customers (400+) use it mostly on windows.
I more and more consider it a bug of webstart to fail.
You can change the temp folder to anywhere you like. But you (or an admin) can change the write permission of that folder. After that webstart fails to start any program.
Problems are mostly in a Citrix environment with a group of customers.
After a normal java install (by an admin) on this systems the temp folder is not writable by the users. A good sysadmin should know this of course.
I think Java should not fail but prompt the user to select another temp folder in case it cannot write to the temp folder.
|
|
|
|
|
java.net RSS
