242AlmMaint Branch Change Log

Owned by Andrew Petro
Last updated: Aug 28, 2007Version comment
1 min read

The 2.4.2 ALM maintenance branch does not have a corresponding Jira project or issues because it is not a main branch targeted towards project deliverables. It is instead a maintenance branch.

This page serves to record a changelog of commits to the branch.

  • alm_242_7 : Detect repeated nodes in recursive calls in AggregatedLayoutManager. Oddly, node ID 1 appears to legitimately repeat. Andrew Petro doesn't presently actually understand this, but he can code around it and has done so. Anyone understanding why this exception is needed, please speak up.
  • alm_242_6 : Logging enhancements to AggregatedLayout (toString() for important ALM layout objects, trace level logging around methods.)
  • alm_242_5 : Eliminated GuidGenerator in favor of a synchronized serial number in AggregatedLayoutManager. Eliminated IUserLayout getCacheKey()
  • Applied fix to UP-1164 to stitch back together the doubly linked list of sibling layout nodes
  • alm_242_4 : Detect and fail on infinite loop in AggregatedLayout getFirstSiblingNode() and getLastSiblingNode() per UP-1683
  • alm_242_3 : Modified AggregatedLayoutManager moveWrongFragmentsToLostFolder() to not call getLayoutNode(null) in the case where getIncorrectPushedFragmentNodes() returns a Collection containing null.
  • alm_242_2 : Added detection of node ID mapping to null node in AggregatedLayout.getLastSiblingNode() and AggregatedLayout.getFirstSiblingNode() and in calling code. This is intended to mitigate one possible source of layout corruption. Special thanks to Michael Oltz for pointing out this potential NPE.
  • alm_242_1 : Removed RDBMServices.supportsOuterJoins , since ALM always set it to false. This doesn't improve ALM's behavior any, but it greatly simplifies the code for further maintenance.