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

checkRendering message should also mention XHTML tags as a possible cause

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

Details

    Description

      When working in development mode with warnings turned on, it's not uncommon to get an error message like the one below when components are added in code, but not found in markup.

      "org.apache.wicket.WicketRuntimeException: The component(s) below failed to render. A common problem is that you have added a component in code but forgot to reference it in the markup (thus the component will never be rendered)."

      This is useful, but doesn't go far enough when assisting new developers. Another common cause that I've seen often is a component is defined and added in a parent class (e.g. AbstractBasePanel), but the child class markup file is missing the <wicket:extend> elements.

      I would like to see the messaging include a statement like: "If your components were added in a parent Page or Panel, make sure the markup for your child MarkupContainer includes the appropriate Wicket XHTML tags such as <wicket:extend>."

      Attachments

        Activity

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

          People

            mgrigorov Martin Tzvetanov Grigorov
            snekse Derek E
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 1h
                1h
                Remaining:
                Remaining Estimate - 1h
                1h
                Logged:
                Time Spent - Not Specified
                Not Specified

                Slack

                  Issue deployment