[WICKET-320] don't keep references to Font and Color in DefaultButtonImageResource

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0 branch (discontinued), 1.3.0-beta1
• Component/s: wicket
• Assignee: Eelco Hillenius
• Reporter: Eelco Hillenius
• Created: 24/Feb/07 00:19
• Updated: 24/Feb/07 04:01
• Resolved: 24/Feb/07 04:01

Description

See if we can get rid of the Color and Font fields in DefaultButtonImageResource. For starters, they are quite heavy and even though they are serializable, they are probably heavier than we would want. Furthermore, at this time they are a problem for clustering with Terracotta. This may or may not be fixed, but we can probably do our bit to avoid keeping those references.

What we should investigate is whether we can store the relevant data of the Font and Color instances, keep that and reconstruct the actual Font and Color instances just when we needed (which should only be during the processing of a request cycle.