OpenJUMP packages
This page offers unofficial packages of OpenJUMP with various deegree related plugins. Older packages from 2008 and 2009 may be found in the archive.
Here you'll find a bunch of pseudo-releases/packages that can be used as a reference. These releases have a version, which often (but not always) correspond to the config tool version used for packaging. The packages won't be deleted, so they can be used subsequently if one turns out to be a sufficiently stable combination.
The custom releases consist of a certain combination of plugins. In particular, they consist of the following:
- an OpenJUMP version
- a deeJUMP plugin
- a WFS-Plugin
- an OWSConfig-Plugin
- the required libraries
They are missing:
- libraries to run the raster tree builder (you can just copy them to the lib folder, if you want to use this feature)
1. Package 1.1.13
- OpenJUMP version: svn revision 2165
- deeJUMP version: This is the deeJUMP plugin, version 1.0.0-dev.
- WFS-Plugin version: This is the OpenJUMP WFS-Plugin version 1.1.1-dev.
- OWSConfig-Plugin version: Your OWSConfig Plugin is a 1.1.12.
- deegree2 version:
- deegree version: 2.5-pre (2010/11/08 16:41 build-28-unofficial)
revision 27836 of svn+ssh://aschmitz@wald.intevation.org/deegree/base/trunk
- deegree version: 2.5-pre (2010/11/08 16:41 build-28-unofficial)
If you wish to use the configuration tool/service, download the service here.
2. Package 1.1.12
- OpenJUMP version: svn revision 2031
- deeJUMP version: This is the deeJUMP plugin, version 1.0.0-dev.
- WFS-Plugin version: This is the OpenJUMP WFS-Plugin version 1.1.1-dev.
- OWSConfig-Plugin version: Your OWSConfig Plugin is a 1.1.12.
- deegree2 version:
- deegree version: 2.5-pre (2010/08/31 12:11 build-26-unofficial)
revision 26278 of svn+ssh://aschmitz@wald.intevation.org/deegree/base/trunk
- deegree version: 2.5-pre (2010/08/31 12:11 build-26-unofficial)
If you wish to use the configuration tool/service, download the service here.
3. Package 1.1.11
- OpenJUMP version: svn revision 2010
- deeJUMP version: This is the deeJUMP plugin, version 1.0.0-dev.
- WFS-Plugin version: This is the OpenJUMP WFS-Plugin version 1.1.1-dev.
- OWSConfig-Plugin version: Your OWSConfig Plugin is a 1.1.11.
- deegree2 version:
- deegree version: 2.5-pre (2010/08/18 09:59 build-21-unofficial)
revision 25942 of svn+ssh://aschmitz@wald.intevation.org/deegree/base/trunk
- deegree version: 2.5-pre (2010/08/18 09:59 build-21-unofficial)
If you wish to use the configuration tool/service, download the service here.
4. Package 1.1.10
- OpenJUMP version: svn revision 1968
- deeJUMP version: This is the deeJUMP plugin, version 1.0.0-dev.
- WFS-Plugin version: This is the OpenJUMP WFS-Plugin version 1.1.1-dev.
- OWSConfig-Plugin version: Your OWSConfig Plugin is a 1.1.8-pre.
- deegree2 version:
- deegree version: 2.4-pre (2010/07/08 10:45 build-18-unofficial)
revision 25195 of svn+ssh://aschmitz@wald.intevation.org/deegree/base/trunk
- deegree version: 2.4-pre (2010/07/08 10:45 build-18-unofficial)
If you wish to use the configuration tool/service, download the service here.
5. Package 1.1.9
- OpenJUMP version: svn revision 1961
- deeJUMP version: This is the deeJUMP plugin, version 1.0.0-dev.
- WFS-Plugin version: This is the OpenJUMP WFS-Plugin version 1.1.1-dev.
- OWSConfig-Plugin version: Your OWSConfig Plugin is a 1.1.8-pre.
- deegree2 version:
- deegree version: 2.4-pre (2010/06/18 10:53 build-17-unofficial)
revision 24933 of svn+ssh://aschmitz@wald.intevation.org/deegree/base/trunk
- deegree version: 2.4-pre (2010/06/18 10:53 build-17-unofficial)
If you wish to use the configuration tool/service, download the service here.
6. Package 1.1.7
- OpenJUMP version: svn revision 1849
- deeJUMP version: This is the deeJUMP plugin, version 1.0.0-dev.
- WFS-Plugin version: This is the OpenJUMP WFS-Plugin version 1.1.1-dev.
- OWSConfig-Plugin version: Your OWSConfig Plugin is a 1.1.7.
- deegree2 version:
- deegree version: 2.4-pre (2010/01/21 14:16 build-33-unofficial)
revision 22094 of https://wald.intevation.org/svn/deegree/base/trunk
- deegree version: 2.4-pre (2010/01/21 14:16 build-33-unofficial)
If you wish to use the configuration tool/service, download the service here.
7. Package Archive
Older OpenJUMP packages may be found in the archive.
FAQ
Question: I use Ubuntu/Gnome and when I start OpenJUMP I get an empty white window. When I move the mouse, the cursor shows different mouse symbols, but nothing else appears in the window. The log shows some problems with i18n, but everything else looks ok. I use Java 1.5.
Answer: It is unknown why this problem appears, probably something with the x server/window manager and the Java 2D display engine. People have reported problems with Java 1.5.0_13. The solution is to use Java6, where the problem seems to be fixed.
Question: I removed/deleted a service from the config tool under Windows, and tried adding a new service with the same name again. It complains that the context/service already exists, but I just removed it...
Answer: The Tomcat under Windows has the problem that the deegree2.jar is not deleted when a service is removed. So you'll end up with a context directory that only contains the deegree2.jar under WEB-INF/lib, and if you try to add a new service with the same name, it still finds the directory. The problem is that even for stopped services Tomcat locks the deegree2.jar, and that's why it cannot be removed. The only feasible workaround is to stop the Tomcat completely, remove the directory, and start the Tomcat again. To do so programmatically might be possible, but is a problematic solution for situations where the Tomcat runs as a different user, on different OS and so on, so it's not implemented. Using a different OS also solves the problem.
Another possible solution was pointed out by our Dutch colleagues. In the context.xml in the conf directory of the tomcat, add antiJARLocking="true" antiResourceLocking="true", and tomcat does not lock the .jars any more.
The third solution is to use package 1.0rc13 or later, where the problem is fixed by default, by including such a context.xml in the template.war. This also fixes the problem pointed out in the next question!
Question: I changed the context.xml as described above, and now editing services and/or users does not have any persistent effect!
Answer: At least under Windows, Tomcat copies the whole webapp into its temporary directory and deploys it from there. This has the unfortunate effect, that the path of the context is now something like temp\0-cfg\WEB-INF.... Since the configuration tool/service stores and alters its configuration file in WEB-INF\conf\services|users, the temporary copies are modified now. You can solve the problem by explicitly setting the path to the config files, like ..\..\..\webapps\cfg\WEB-INF\conf\services. Absolute paths are NOT supported here at the moment!