If you’ve run in to the error:

“org.apache.wicket.markup.MarkupNotFoundException: Can not determine Markup. Component is not yet connected to a parent”

Searches online typically don’t yield very much. They tend to give the hint and reiterate what others have found: The HTML file is either misnamed, the resolving component fails to find the corresponding HTML file to the Wicket java class, or that the HTML files are not included in the WAR. They don’t offer very many solutions. However in my situation, using Maven, the issue was resolved by including resources reference in the build section:

       

           

                false

                src/main/resources

            </resource>

          **  **

                false

                src/main/java

**                **

                    **

                </includes>

**                **

                    **/*.java

                </excludes>

            </resource>

        </resources>