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

Fragment fails to report an error in development mode

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 6.24.0
    • 8.0.0-M2, 6.25.0, 7.5.0
    • wicket
    • None

    Description

      Fragment under certain circumstances fails to report errors while in development mode.

      In my case Fragment had the same id as markupId. Probably this should be allowed but in this case it triggers a bigger problem, it is silently ignored errors and even works in development, and fails in deployment mode.

      To trigger this bug, fragment must be inside a TransparentWebMarkupCotainer and <wicket:child>. If we leave out either TransparentWebMarkupCotainer or <wicket:child> it works, i.e. fails with correct message in either mode.

      Please check attached sample project that exhibits this behavior. Try an run it with a different configuration type.

      Attachments

        1. fragmentbug.zip
          42 kB
          Octavian Ciubotaru

        Issue Links

          is related to

          Task - A task that needs to be done. SYNCOPE-962 Upgrade to Wicket 7.5.0

          • Major - Major loss of function.
          • Closed

          Activity

            People

              pedrosans Pedro Santos
              developster Octavian Ciubotaru
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: