• New Feature
  • Status: Closed
  • 1 Critical
  • Resolution: Fixed
  • X-Common Code
  • teck
  • Reporter: drb
  • November 30, 2006
  • 0
  • Watchers: 0
  • July 27, 2012
  • February 23, 2007


When a non-portable exception is encountered, the specific object that tripped the error is not always the best one to declare as a DSO transient field. Sometimes an object higher up the graph is a more logical choice. To make it easier to identify the most appropriate object to exclude from sharing, Sessions Configurator should display the whole known object graph on non-portable error.


* Show object graph containing the offending object
* All parent objects of the offending object should be expanded
* Highlight (possibly in red) the offending object
* Position the highlighted object for easy viewing (possibly in center of page)
* If information about other offending object is available, highlight them too (possibly in yellow)

You set a root and fire up your client. No locks, no transients, no bootjar classes. Errors are logged and at shutdown a suggested config file is spit to the log, or the specified config file is just updated. This could be the development mode of operation.


Fiona OShea 2007-02-07

Updating Due date to last day of Moraga dev iteration

Tim Eck 2007-02-23

this is done now. There is a textual representation of the graph logged to the TC log file whenever one attempts to share a non-portable type. The graph is adorned with markers showing all of the non-portable instances in the graph.

This logging in on by default, but can be disabled with the option in the the section of the config file