* REPO-3962: Remove context refresh from testOpenCloseOpenCloseFull
* The refreshing of minimal context does not work with Spring version greater than 5.1.0
* We don't need to test refreshing the core application context as that never happens, only the subsystem application contexts are refreshed
* REPO-3962: Add test for application context refresh
* Test is disabled for now until the bug in Spring is fixed
* [SEARCH-799] Added WeakFilteringSetResult class. This type of filtering does not concerns permissions and allows to access to the tolal number of elements.
* [SEARCH-799] Added nested filter in. The inner one is for permission filtering and the outer one if for count filtering.
The change concerns the case of optimisePermissionsCheck=true.
* [SEARCH-799] Implemented double filtering when optimizePermission=false. Code refactoring.
* [SEARCH-799] Fix problem in resultSet.length() resulted in org.alfresco.opencmis.CMISTest#testQueryNodesWithCorruptedIndexes test.
* [SEARCH-799] Added unit test for pagination result.
* Syntax fixes.
* Removed import *.
* Set back system user as current user.
* [SEARCH-799] added Javadoc and some useful description in test methods.
* [SEARCH-799] Added javadoc
* [SEARCH-799] Code refactoring and some comments.
* [SEARCH-799] Code refactoring.
* Reverted changes for REPO-3743 #276
* Changes in PersonService to ensure a consistent behaviour for the System case:
- PersonService.createPerson() throws now an AlfrescoRuntimeException when trying to create a person for the username 'System'
- PersonService.getPerson("System") throws NoSuchPersonException
- PersonService.personExists("System") returns false
* Remove StandardRenditionLocationResolverTest tests from the suite - the RenditionService deprecated, so related tests won't be maintained
* Fixes for the System user case in ImapService
* Update alfresco-data-model 8.27
Bumps `dependency.camel.version` from 2.23.0 to 2.23.1.
Updates `camel-spring` from 2.23.0 to 2.23.1
Updates `camel-amqp` from 2.23.0 to 2.23.1
Signed-off-by: dependabot[bot] <support@dependabot.com>
The reject action in RM triggers an email notification from repo. Code in EMailNotificationProvider.buildTemplateModel(...) requests for the person associated with the current authenticated user.
Potentially another bug in Repository.getPerson() (next call in the stack trace), considers the current user to be AuthenticationUtil.getRunAsUser(), instead of the fully authenticated one. This calls, down the line, for the retrieval of the person for the username System, which ends up in trying to actually create the user System (which is not permitted), hence the exception.
The most simple (and safe) fix was to add a check for username System, in the low-level method PersonServiceImpl.getPersonImpl(...), and return null or throw NoSuchPersonException.
2 tests were added, for the Person service and for the email notification generation.
* RM-6141: RM_support_for_the_Insight_Engine
Pass filter queries in SQL requests to the Insight Engine.
* SEARCH-1351 Add unit tests for SolrSQLHttpClient.
This involved changing the return type of postSolrQuery. The cast
taking place in this file did not make sense to me, since the two
types are not in the same type hierarchy. However it is obviously
working at the moment, so I have simply moved the location of the
cast. I couldn't find any references to the protected method anyway,
so it did not seem risky to update.
* SEARCH-1351 Add new unit test file to suite.
* SEARCH-1351 Remove unused test variables and fix logging.
