Gentics .Node Changelog Summary

Gentics .Node 2.0.5


Bugfix RT58293

Registering mccr datasources with the old sanitycheck (which is used by default) failed, because sanitycheck is not compatible with mccr datasources. The behaviour has been changed now, sanitycheck will not be used for mccr datasources any more. If checking the database is required for mccr datasources, sanitycheck2 should be used instead.


Gentics .Node 2.0.4


Bugfix RT58236

MCCR: Fixed error “Error while setting value for attribute” that occured in GPN 4.6.0 when cache warming is enabled or a frontend page was loaded.


Gentics .Node 2.0.3


Bugfix RT58194

GenticsImageStore: A StringIndexOutOfBoundsException was fixed when processing an image Url with a very long filename.


Bugfix RT58193

GenticsImageStore: A StringIndexOutOfBoundsException was fixed when processing an image Url with a missing file extension. The mimetype-detection for the image is now done by looking up the file content.


Gentics .Node 2.0.2


Bugfix RT58202

An StringIndexOutOfBoundsException was fixed inside the non-api fileutils.


Gentics .Node 2.0.1


Enhancement

Some no longer needed third party dependencies were removed. Previously the org.eclipse.core.runtime dependency was included. We now only include the org.eclipse.equinox.common dependency.


Bugfix RT51435

When creating a datasource using the PortalConnectorFactory based on handle properties and datasource properties fails, no open handle will be left behind.


Gentics .Node 2.0.0


Java Project Structure Changes
Various changes to the internal Gentics .Node project structure have been made. These changes might affect existing build setups that make use of the provided maven artifacts.

  • The java source code for this project will now be compiled for JDK 1.7. Gentics .Node classes are no longer executable with JDK 1.6 and older JDKs.
  • Various maven dependencies were moved from node-lib to contentnode-lib and portalnode-lib.
  • The restapi-lib module was removed. It is now a part of contentnode.

Enhancement

When creating a new datasource using the PortalConnectorFactory, the datasource will no longer be checked with autorepair by default if neither the autorepair nor the autorepair2 flags are set for the datasource. It is recommended to always use the autorepair2 flag for the datasource to check and repair datasources.