123386 adavis: MNT-14295 TransformerConfigLimits Behavior Differs on Java 7 vs 8
- Fix TransformerConfigLimits.setTransformationLimitsFromProperties(...)
so that it does not clear the limit (e.g. readLimitTimeMs) when setting
the max value (e.g. timeoutMs) or the other way around. It is normal to
have both values defined for the default.transformer.
- This has been a problem since 4.2.
- The problem only came to light with the switch to Java 8, as the order in which
transformer properties are loaded changed. They were being loaded in MapEntry order.
The problem did not show up in the unit tests, because they too were impacted by
the MapEntry order and ironically loaded the properties in the same order.
- Added unit tests that are not impacted by MapEntry order.
- Enhanced the debug and toString methods in order to trace the problem.
git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/alfresco/BRANCHES/DEV/5.1.N/root@123402 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261