When RESTXQ detects a security error, it should not fail with a 500.
Instead initiate a basic auth handshake (401), so that the
user can retry the request with the correct level or authorisation.
Use the existing authenticator, instead of cooking up a new one.
improve exception message
Merge pull request #145 from shabanovd/develop

improve exception message
[performance] Redesign query optimizer for operations using range index (comparisons, contains, starts-with...): split query rewriting into two parts: 1) inject pragma (for top-level optimizations) and rewrite filter expressions to use range functions, 2) check at runtime if optimization can be applied (index is available) or not. Fall back to default processing if no index available.

This approach should be more expensive than the compile-time optimization we used before, but has the advantage that queries do not need to be recompiled if the collection configuration changes. The overhead for rewriting the query on the fly was not measurable in my tests though (below the threshold of the profiler).
[performance] When reindexing a collection, trigger a sync on the lucene-based indexes after the collection indexes got removed and before updated data is saved.
Merge branch 'develop' of https://github.com/eXist-db/exist into develop
Merge pull request #146 from wolfgangmm/develop

Redesign query rewriting for index operations
Merge pull request #133 from Infiniverse/fix-restxq-401

When RESTXQ detects a security error, it should not fail with a 500.
[feature] For all serialization functions: allow serialization parameters to be specified as XML as defined by standard fn:serialize function.
[ignore] Fix serialization options in old, xml-based test runner
Merge pull request #148 from wolfgangmm/develop

Make serialization functions more consistent
[bugfix] fn:doc overwrites dependencies. It should not.
Merge pull request #149 from wolfgangmm/develop

[bugfix] fn:doc overwrites dependencies. It should not.