Fragment fails to report an error in development mode

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.