[TAP5-1110] Tapestry holds onto the verbose descriptions of component class transformations, causing a memory leak

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.2.0
• Fix Version/s: 5.2.0
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 21/Apr/10 09:24
• Updated: 21/Apr/10 09:46
• Resolved: 21/Apr/10 09:46

Description

As noted, since they are logged, there's no advantage to keeping them in memory. Further, the new approach to class transformation in 5.2 means that component class transformation is more uniform and less hard to debug.