[WICKET-1975] Allow custom form components to be more easily created by removing final from certain methods.

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.5.0
• Component/s: wicket
• Assignee: Unassigned
• Reporter: Larry Zappaterrini
• Created: 09/Dec/08 22:23
• Updated: 02/Apr/12 14:02
• Resolved: 02/Apr/12 14:02

Description

I was perusing Wicket's Javadocs and I came across a link to an old thread: http://www.nabble.com/Why-add%28IBehavior%29-is-final--td7248198.html#a7248198

The issue in that message thread was resolved by WICKET-94 with the final modifier being removed from from Component#add(IBehavior). I am currently trying to do something similar to the original author of the thread and I believe the same concession should be extended to FormComponent#add(IValidator) and FormComponent#setFieldType(Class<?>) due to similar arguments. In fact, might it make sense to look though the public final methods of FormComponent and only make final those that are absolutely necessary from an encapsulation standpoint?