edgar soldin wrote:
> On 22.04.2012 21:07, Matthias Scholz wrote:
> > Hi,
> >
> > I've commited a small fix in the AboutDialog. If the
> "readme.txt" file
> > was not found, the Stacktrace was shown. This is bad if you
> run OJ as
> > Webstart. Now nothing is viewed.
> actually not finding the readme.txt right now is an error,
> except when developing. that's why i left the stack there.
> >The problem with Webstart is, that the
> > classpath is only the jre/lib/deploy.jar. So we cannot load
> readme.txt
> > from classpath :-(
> are you sure there is no way for a webstart application to
> load a file either from a webserver or from an external archive?
I had a quick look on the jnlp files we are using. A few years ago I used to
maintain some configuration files and image catalogues of one of our
applications which had all those files packaged into a single jar. When the
application was updated I placed all current configuration files into a new
jar, signed it with the same computer than all the other jars and replaced
outdated jars from the application server. For the maintainer it is not so
convenient because every little change in one file means repackaging and
signing the new jar. For the users it works well as long as everybody is happy
with the exactly same settings.
We have also another application that is based on uDig which is launched
through JWS. I see that that application is saving user preferences into a
local directory. The location of user data is given in the launching jnlp file
as in resources/property as
<property
name="osgi.instance.area"
value="c:/data/application"/>
Application creates initial configuration files into this data directory but
they are not overwritten later and thus users can use some individual settings
which remain even after updates.
JWS is a nice idea but it is a bit complicated to use in managed environment.
For example the data dir location above means that all the users must have
rights to create the c:/data/application directory and read/write/execute files
inside it. Some of our users did not have write access to C: drive at all which
made some pain. Also the proxy settings of JWS launched applications must be
set through the Java settings in the control panel which is not so obvious.
Anyway I would be interest to serve OpenJUMP through JWS also from my server
when Matthias discovers how to make the tools menu available.
-Jukka Rahkonen-
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
Jump-pilot-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
