great and thanx for looking into it! so lets see what Jukka sais tomrrow or tuesday if it works we are kind of ready for a OJ 1.3 release. I will copy then next week the missing Portuguese chars from the Brazil file, update the version number, and setup the build (haven't done that for over a year now, so it may take some time to readjust ;)
stefan Michaël Michaud wrote: > Hi, > > Probably related to a change I did in Layer class, but cannot reproduce > exacly the bug you describe. > > I tried to load a postgis table and get the folowing error : > > com.vividsolutions.jts.util.AssertionFailedException: If this event is > being fired because you are constructing a Layer, cat will be null > because you haven't yet added the Layer to the LayerManager. While > constructing a layer, you should set firingEvents to false. (Layerable = > troncon_de_route) > at com.vividsolutions.jts.util.Assert.isTrue(Assert.java:71) > at > com.vividsolutions.jump.workbench.model.LayerManager.fireLayerChanged(LayerManager.java:446) > at > com.vividsolutions.jump.workbench.model.AbstractLayerable.fireLayerChanged(AbstractLayerable.java:95) > at > com.vividsolutions.jump.workbench.model.Layer.setFeatureCollectionModified(Layer.java:541) > at > org.openjump.core.ui.plugin.datastore.AddDataStoreLayerWizard.load(AddDataStoreLayerWizard.java:115) > > I could solve this error (may be related to the last change I did in > Layer class), and now it works for me. > > Your stacktrace tell that there is no name for your layer > I can get the same stacktrace if I click finish without selecting a > dataset from my database. > Can you try again from nightly build after one day or two and confirm > the error. > > Michaël > > Stefan Steiniger a écrit : >> 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 >> >> >> > > > ------------------------------------------------------------------------------ > _______________________________________________ > 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
