Rethink locking support within deegree #1259
Labels
contributions welcome
asking for contribution (time and money sponsor)
dependencies
Pull requests that update a dependency (library)
funding welcome
financial sponsoring wanted (money)
TMC discussion
to be discussed by technical management committee members
We are currently using H2 to implement local locking. Given that this is the only thing we use H2 for we should rethink this strategy. We should at least be able to drop the H2 dependency as this would resolve #1250.
The WFS should use the locking functionality provided by the database backing the FeatureStore and when a file based FeatureStore is in use we could consider refusing locking requests.
The text was updated successfully, but these errors were encountered: