Gentics Content.Connector Changelog Summary

Gentics Content.Connector 2.2.5


Bugfix

Isolate the Velocity-runtime for the contentconnector. The contentconnector will now use
the new-able VelocityEngine class internally instead of the Velocity class singleton.
This ensures that the configuration of the Velocity engine in the contentconnector will
not interfere with that of other libraries or frameworks which use (and configure) the
singleton model.


Gentics Content.Connector 2.2.4


Enhancement SUP-3060

Add new LDAPRequestProcessor. This RequestProcessor can be used to access LDAP entries
via the Gentics ContentConnector. For usage in the Lucene indexer see the
deact_indexer.ldap.properties file in the config-sample.


Bugfix

The NavigationCacheRequestProcessor has been fixed to get the navigation synchronously,
if it is not found in the cache, instead of returning null.


Bugfix

The node version has been updated to 2.3.1. This node version includes a fix for multithreaded access of
caches for contentobjects.
Also the version of the trove library has been updated to 2.1.0.


Gentics Content.Connector 2.2.3


Bugfix

The dependencies have been cleaned again to avoid some more errors
due to conflicting libraries.


Gentics Content.Connector 2.2.2


Bugfix

The dependencies have been cleaned to avoid various errors
due to conflicting libraries.


Gentics Content.Connector 2.2.1


Bugfix

The node version has been increased to 2.1.2. This node version does not use quartz for scheduling of
datasource related background jobs. Due to a version conflict of quartz, sometimes the background jobs were
not scheduled (without any error message), and clearing the caches due to changes in the contentrepository did not work.


Gentics Content.Connector 2.2.0


Security

Updated the dependencies org.apache.poi and org.apache.tika to their latest versions in order to fix the security vulnerabilities CVE-2014–3529 and CVE-2016–5000


Enhancement

The delimiter used in the transformer SimpleMVString to join values can now be configured.
The previous static delimiter, a whitespace, is now the default delimiter.
The use of stopwords can now be toggled in CustomPatternAnalyzer. Stopwords are enabled by default.