Hei Jukka, thanks for reporting. As far as i can see the last change was done by Michael in Layer - which changed the layer property to changed by default (so that OJ always askes for storing if closed). However, I don't see why this would cause a problem.
But interestingly - the line given in the stacktrace for the error in the Layer class (Line 98) is also invalid ... maybe there is another (compiler?) problem. As I don't have postgis setup (yet) I can't look into it right now ... maybe in the next 2-3 weeks (depending on my april schedule) seems like we need to fix this is issue before any OJ 1.3 release stefan Rahkonen Jukka schrieb: > Hi, > > As reported earlier, there is now something wrong with adding database layers > to OpenJUMP project. A trial fails with error message: > com.vividsolutions.jts.util.AssertionFailedException > at com.vividsolutions.jts.util.Assert.isTrue(Assert.java:68) > at com.vividsolutions.jts.util.Assert.isTrue(Assert.java:54) > at > com.vividsolutions.jump.workbench.model.AbstractLayerable.<init>(AbstractLayerable.java:64) > at com.vividsolutions.jump.workbench.model.Layer.<init>(Layer.java:98) > at > org.openjump.core.ui.plugin.datastore.AddDataStoreLayerWizard.createLayer(AddDataStoreLayerWizard.java:90) > at > org.openjump.core.ui.plugin.datastore.AddDataStoreLayerWizard.run(AddDataStoreLayerWizard.java:65) > at > org.openjump.core.ui.plugin.file.OpenWizardPlugIn.run(OpenWizardPlugIn.java:93) > at > com.vividsolutions.jump.workbench.ui.task.TaskMonitorManager$TaskWrapper.run(TaskMonitorManager.java:149) > at java.lang.Thread.run(Unknown Source) > > However, if I open old stored projects with database layers they still work > OK. Probably the fault is not extremely big and difficult to cure if only > someone finds where it is. > > I noticed that if database layer contains WHERE query it is also stored into > JUMP project file like > <mapping> > <key class="java.lang.String">Where Clause</key> > <value class="java.lang.String">highway='primary'</value> > </mapping> > > That made me to think that when showing database layer properties perhaps the > WHERE clause could be showed as well, and even better, it might be editable. > > -Jukka Rahkonen- > > > ------------------------------------------------------------------------------ > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > ------------------------------------------------------------------------------ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
