* REPO-4753: remove com.google.mp4parser:isoparser dependency
This dependency is not required in this project and triggers some conflicts in other projects (tika) due to the difference of versions.
* SEARCH-2074: Add new queries tests to ensure these ANSI SQL queries work with different database engines.
* SEARCH-2074: Check returned values from queries instead of asserting the value is not null.
* SEARCH-2074: Next TX Commit Time should be greater or equals to from commit time.
The MNT-18895 ticket has highlighted the fact that behaviour filter service did not have an extension when it comes to smart folders.
The issue had to do with the creation of renditions as children of documents, when a document hasn't got any rendition yet, and the rendition is created as a new node from a smart folder, it is only the virtual node that gets its aspect cm:auditable disbaled and not the actual node linked to it.
The cm:auditable is responsible for certain updates of node's properties, in particular the properties cm:modifier and cm:modified.
This merge delivers an extension for behaviour filter service as it is the case already for other services (node, coci, lock, fileFolder..)
* Extension of the BehaviourFilter service for smart folders:
- VirtualBehaviourFilterExtension: specific implementation of BehaviourFilter service, executed in smart folder context
- BehaviourFilterExtension/BehaviourFilterTrait/annotations on top of override BehaviourFilterImpl methods: allow AOP mechanism
- smartfolder-context: declaration of the new beans and injection into the virtualisation bundle
- VirtualBehaviourFilterExtensionTest and AppContextExtraTestSuite: to ensure that the extension is used instead of the original implementation
(cherry picked from commit 9399a743fd)
The MNT-18895 ticket has highlighted the fact that behaviour filter service did not have an extension when it comes to smart folders.
The issue had to do with the creation of renditions as children of documents, when a document hasn't got any rendition yet, and the rendition is created as a new node from a smart folder, it is only the virtual node that gets its aspect cm:auditable disbaled and not the actual node linked to it.
The cm:auditable is responsible for certain updates of node's properties, in particular the properties cm:modifier and cm:modified.
This merge delivers an extension for behaviour filter service as it is the case already for other services (node, coci, lock, fileFolder..)
* Extension of the BehaviourFilter service for smart folders:
- VirtualBehaviourFilterExtension: specific implementation of BehaviourFilter service, executed in smart folder context
- BehaviourFilterExtension/BehaviourFilterTrait/annotations on top of override BehaviourFilterImpl methods: allow AOP mechanism
- smartfolder-context: declaration of the new beans and injection into the virtualisation bundle
- VirtualBehaviourFilterExtensionTest and AppContextExtraTestSuite: to ensure that the extension is used instead of the original implementation
