* In node browser:
** Added macro convertToJSON to recursively parse hashes and enumerables
** Added attempt/recover in macros to handle errors and not break the page
** Changed the output of serialized objects to JSON format
* In both admin console and node browser:
** Adjusted consistency of the ouput when an error occurs
** Validate the depth of each hash. When we find a hash with over 1000 elements, we throw an error instead of displaying the object. Used the stop tag to effectively force an abort of the template processing preventing performance or security issues regarding very large objects.
* SEARCH-2909 Return Http Status Code 501 (Not Implemented) in REST API for invocations to Search Services that are not supported.
* SEARCH-2909 Refactor exception mapping to simplify QueryParserException.
* SEARCH-2909 Add unit tests for postQuery.
This includes a test for the status code replacement with unsupported operations.
* SEARCH-2909 Add new unit test file to test suite.
Also add copyright header to test class.
Co-authored-by: Tom Page <thomas.page@alfresco.com>
* SEARCH-2802: Filter HTTP requests (now "none" and "secret" communication methods are available) from X509 Web Filter.
* SEARCH-2802: HttpClientFactory (for Repository and Search Services clients) support for Shared Secret communication.
* SEARCH-2802: Fix HttpClientFactory base unit tests.
* Added macro convertToJSON to recursively parse hashes and enumerables
* Added attempt/recover in macros to handle errors and not break the page
* Changed the output of serialized objects to JSON format
* REPO-5376 Remove all temporary code
* Remove DBStats, SingleTaskRestartableWatch
* Remove propertiesCache and aspectsCache from DBQueryEngine as they were marked as temporary
* Remove further temporary code
Co-authored-by: Nana Insaidoo <insaidoo.nana@yahoo.it>
* * more filter implementation
* * aspect test case added
* * fixed coments and more test added
* * comments fixed
* * import and data fixed
* * removed unnecessary filter
* [SEARCH-2677] Extract SearchEngineResultSet and SearchEngineResultMetadata interfaces
* [SEARCH-2677] Scan the ResultSet decorator chain for a maximum of 3 nested levels
* MNT-14308: CMIS - optionally request rendition(s) when uploading docs - part 2
- note: PublicApiAlfrescoCmisServiceFactory extends AlfrescoCmisServiceFactory and overrides getCmisServiceTarget
- hence, also ensure property (cmis.create.doc.request.renditions.set) is set for public rest api spring context
- note: set following log4j.properties: log4j.logger.org.alfresco.opencmis=info
* MNT-14308: CMIS - optionally request rendition(s) when uploading docs - part 2
- tweak info log to output property on init (since service currently instantiated on every call)
- note: set following log4j.properties: log4j.logger.org.alfresco.opencmis=info
- group jakarta dependencies in the POMs
- define explicit version properties for the various jakarta APIs
- replace all *javax* libraries with their *jakarta* equivalent
- exclude all *javax* libraries brought in by our dependencies (they can't be handled through _dependencyManagement_ due to the different jar names)
- upgrade the *jakarta* libraries to the latest versions that still use the _javax_ package namespace
Provides hook points for the query accelerator in alfresco-enterprise-repo.
In addition to these, it also includes temporary code to add timing headers to REST API calls. These will be removed as part of REPO-5376.
Commits mainly by Bruno and Nana. Merging from old projects and changes from master by Alan.
Now that the T-Engines provide parity with in process legacy transforms and metadata extract, the legacy transform code is now being removed. This will allow the documentation to be greatly simplified and a number of libraries to be removed.
Custom legacy transforms need to be moved to T-Engines. ACS 6 still provides a version where both may be run in parallel. New versions of the document transform engine (DTE) and media management (MM) are planned for ACS 7.
* ACS-976 Metadata extraction NPE thrown in multi-node cluster using ATS
In a multi repo node cluster, it is possible one node requests a metadata extract via the ATS and
that another responds to it. In this case the responder needs to recreate the TransformRequest. In
this case the target mimetype was wrong, resulting in the TransformRequest being sent to the wrong
code which then through a NPE because there was no replyQueue specified on the TransformRequest.
* ACS-963 Investigate testSharedLinkCreateGetDelete failures
Modified date changes. It can change now as metadata extract is async
MNT-22036 : REST API always applies versioning
Add property boolean versioningEnabled
Add versioningEnabled to node creation using multipart/form-data
Add versioningEnabled to node creation using JSON
Add unit tests for node creation using JSON.
Changed property String versioningState to boolean versioningEnabled
Add versioningEnabled to node creation using JSON
Add unit tests for node creation using JSON.
Add versionState form-data property to POST nodes/{nodeId}/children multipart upload.
Add versionState to MultiPartBuilder.
Add tests for multipart upload
Removed all the Extractors that now exist in the T-Engines:
JodConnverterMetadataExtracter
TikaPoweredMetadataExtracter – the abstract base class used by other extractors
-- MailMetadataExtracter
-- PoiMetadataExtracter
-- TikaAutoMetadataExtracter
-- MP3MetadataExtracter
-- TikaSpringConfiguredMetadataExtracter - removed as it required Spring config and would run in process
-- PdfBoxMetadataExtracter
-- OpenDocumentMetadataExtracter
-- OfficeMetadataExtracter
-- DWGMetadataExtracter
HtmlMetadataExtracter
RFC822MetadataExtracter
XmlMetadataExtracter and XPathMetadataExtracter still exist but don't provide any extraction out of the box. The reason they still exist is to support custom transforms (in AMPs) to extract from XML. There are no XML extractors in the T-Engines at the moment, but that is where the custom transformer code really should be moved.
There are new tests to ensure the async transforms take place as expected.
Additionally many of the existing tests still exist (those not related to a specific extractor). Some of these have been modified to reflect that the extract is now async and to no longer check the modified value has not changed (it is now expected to change).
There are also a number of new metadata extract smoke tests that ensure that a selected subset of extracts are supported by the OOTB T-Engines.
This PR removes legacy Lucene code and dependency to the lucene 2.4.1 library.
The data type analysers were removed with an exception of the definitions in models (datadictionaryModel.xml and cmisModel.xml) to be backwards compatible with existing components (like older versions of Search Services) and to ensure the current old-style models can still work with repository and pass validation.
