D-Net

[maven-release-plugin] copy for tag dnet-oai-utils-3.3.2

Cache management: it's a mess if we have more than one <cache:annotation-driven> instructions:
- the container now has a dedicated application context for caches
- logs to DEBUG for spring cache module

#1342: added caches to limit the load on exists when a client performs a list of getRecord requests.

idScheme and idNamespace are not a property anymore, but they are dynamically read from the OAI configuration profile

The oai database currently in use is discovered dynamically from the OAIConfiguration profile.
The xquery to use to retrieve the db name from the configuration is in the property services.oai.publisher.db.xquery.
The OAI controller/core have been refactored....

remove definition of SplittedQueryExecutor bean, now defined in cnr-service-common instead. Changed resource annotation to autowired