You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Peter Parson (JIRA)" <ji...@apache.org> on 2013/01/15 12:30:12 UTC

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

Peter Parson created WICKET-4978:
------------------------------------

             Summary: 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


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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira