- ensure that the returned token is always updated. This is currently not the case when there are no more items. The next token is set to null in that case, even though there might be (maxItems-1) results.
- added Junit tests
- removed code that was made useless by previous code changes (see MNT-15338)
- added junit for the case when getAllVersions() is used with null objectId (Cmis WS binding)
* REPO-2182 : Community: ALF-21852: setContentStream() returns the wrong document version when auto-versioning is turned on
Separete into different new transactions writing content from creatingObjectId for setContentStream()
Separate into different new transactions deleteing content from creatingObjectId for deleteContentStream()
Separate into different new transations appending content from creatingObjectId for appendContentStream()
Create JUnit CMISTest.testSetDeleteAppendContentStreamVersioning() testing that set/delete/apped calls return the new version.
REPO-2025 Marked existing tests with categories LuceneTests and DBTests
Also includes a few PerformanceTests. So that the DB tests could be run on their own for each DB, a new
AllDBTestsTestSuite was created and it was tried out with MySQL (REPO-2002), MariaDB (REPO-2005) and PostgreSQL (REPO-2954).
A few existing TestSuites have been removed because we now have AllDBTestsTestSuite or the same set was covered by one of the TestSuites run in the latest Bamboo build jobs.
* REPO-1065 : Service Pack: MNT-16641 CMIS API: Applying aspects including protected properties results in CmisInvalidArgumentException: Property is read-only!
Remove code from CMISConnector.processSecondaryTypes, that for each aspect added, it will search all of his properties in repository and add them with a null value(if not included in the propsToAdd).
Add an extra check to CMISTest.testUpdatePropertiesSetDeleteContentVersioning now adding the P:cm:lockable aspect to a document (before this fix failing).
Added CMISConnector.isUpdatable returns true/false if a property is updatable
