Closed andbue closed 3 years ago
Hi, thanks a lot for testing the dev branch and reporting the bug.
As hinted correctly, the changes to the model – and in particular changing what a Polygon
represents – were the culprit. Adapting the cut action to the new model worked.
Starting from b6a64b7 using the cut functionality should work correctly again.
Great, thanks for the quick fix!
Hi, @chreul asked me to test the dev branch to see if it's ready for production. This is the result: :innocent:
... when opening the test book, adding a "cut line" somewhere on the page and starting "segment". I tried it both on tomcat8 and jetty-maven-plugin with java-8-openjdk.
The problem might be that in the JSON sent from frontend, cuts are now defined like
which looks more like a web.model.Region to me, while here https://github.com/OCR4all/LAREX/blob/57dd0d504413f3aa5193540ee586854f4b808e4b/src/main/java/de/uniwue/web/facade/segmentation/FixedGeometry.java#L24-L26 they seem to be defined as polygons. This leads to polygons where
points
is not defined and thereforenull
, sending me in java exception hell. Unfortunately, it seems like I can't figure out neither how to use Eclipse properly nor how to force fasterxml.JsonCreator to produce valid polygons from this kind of input as well as the default points JSON, so I'm hoping for your ideas how to fix this!