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

["Martin Grigorov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-4978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-4978.
-------------------------------------
    Resolution: Fixed

The original requirement is now covered by the implementation of WICKET-6229.

[~tobiashaupt] I'll move your comment to a new ticket.

> Add possibility to force usage of (renderable) tag for own Components
> ---------------------------------------------------------------------
>
>                 Key: WICKET-4978
>                 URL: https://issues.apache.org/jira/browse/WICKET-4978
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>            Reporter: Peter Parson
>         Attachments: wicketPanel_Tag_Rewriting.zip
>
>
> 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(). 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)