[WICKET-136] Add FormComponentPanel to the core project.

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0 branch (discontinued), 1.3.0-beta1
• Component/s: wicket
• Assignee: Unassigned
• Reporter: Eelco Hillenius
• Created: 03/Dec/06 22:35
• Updated: 16/Dec/06 11:59
• Resolved: 16/Dec/06 11:59

Description

I found it to be quite a common case that you want to have a panel that itself is not a form component in the sense that it actually receives user input, but in the sense that it cooperates with the form processing. A typical use case is a panel that embeds multiple form components but that to the outside world acts like one component with one model. For example: a Date/Time component could have a component for the date and components for hours /minutes /am or pm.

See the attached file for a component that supports such use. It is the simplest version. The end-version should have <wicket:head> parsing in it, but that's only possible with some refactoring.

Sub-Tasks

• Implement FormComponentPanel for 1.3: Resolved
• Implement FormComponentPanel for 2.0: Closed