[WICKET-4978] Add possibility to force usage of (renderable) tag for own Components

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: wicket
• Assignee: Unassigned
• Reporter: Peter Parson
• Created: 15/Jan/13 11:28
• Updated: 18/Nov/16 22:39
• Resolved: 18/Nov/16 22:32

Description

Sometimes, Components don't work as expected when not used with a DOM element.
This generates bugs, which are often and especially only visible on ajax interaction.

Common scenario: updating a component via Ajax which is used with wicket:container or setRenderBodyOnly(true). Or updating those (non-existent) DOM element with HTML attributes.

To allow for fail-fast behavior, I suggest to add an overridable getter to indicate that the component must be rendered as DOM element, e.g. isDomElementMandatory().

Issue Links

• is superceded by: WICKET-6229 Introduce a new setting in ExceptionSettings to control whether to throw exception or log a WARN when requesting for markup id on non-renderable component