Uploaded image for project: 'Wicket'
  1. Wicket
  2. WICKET-4978

Add possibility to force usage of (renderable) tag for own Components

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • None
    • wicket
    • None

    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().

      Attachments

        Issue Links

        is superceded by

        Improvement - An improvement or enhancement to an existing feature or task. 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

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Resolved

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            pparson Peter Parson
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment