Re: Disabling the Sandbox
Thomas Hawtin wrote:
...
Note, you can read (only) files from the path that the your classes are
loaded from.
I suspect that is the problem with the OP's current
attempts, but not knowing the path to the applet,
or the codebase, it is hard to be sure.
...
Applet support in the Java PlugIn and Java WebStart are extensions of
the appletviewer code. There are some technical differences. I think the
class loading is slightly different by default ...
It used to be, but there were a swathe of 'broken* web
start app.' questions in the JWS forum over recent times
when the classloaders for the applet plug-in and web start
(for both applications and applets) was merged into a single
entity.
* Most of those questions were related to finding the
location on disk where the classes were cached, and
that was always a broken and fragile way to go about
finding resources, even before Sun included an option
for the end user to specify the cache location.
Since 'getResource()' and plain URL's always worked
seamlessly, I never bothered to look into it that carefully,
beyond recommending to rework the app. to use them.
...and PlugIn/WebStart, for
instance, allows printing to go ahead after a dialog without any
additional APIs.
Sockets, sure, but I thought the Print API was locked out,
except by use of the PrintService** (had never bothered
checking it though, and frustratingly - do not even have
a printer to test my own JWS example!).
** <http://www.physci.org/jws/#prs>
...
My preferred solution is to run in the sandbox, with the extra
facilities Java WebStart gives you, ...
I suspect that would suffice, for this app., and that
it would therefore by the best choice, ..except for
that tight browser integration. I mean - try and
configure the launch parameters of a web start
app., using JS. ;-)
--
Andrew Thompson
http://www.athompson.info/andrew/
Message posted via JavaKB.com
http://www.javakb.com/Uwe/Forums.aspx/java-general/200708/1