When resource responds with 404 custom error page rendering fails

I have a webapp where the 404 error page is rendered by wicket. The home page contains an image with a dynamic resource. When the resource responds with 404, wicket throws the following exception:

org.apache.wicket.DefaultExceptionMapper - Unexpected error occurred
org.apache.wicket.request.handler.ComponentNotFoundException: Could not find component 'foo' on page 'class wicket.NotFoundPage
at org.apache.wicket.request.handler.PageAndComponentProvider.getComponent(PageAndComponentProvider.java:167)
at org.apache.wicket.request.handler.ListenerInterfaceRequestHandler.getComponent(ListenerInterfaceRequestHandler.java:81)
at org.apache.wicket.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:142)
at org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:715)
at org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:63)
at org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:212)
at org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:253)
at org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:138)
at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:194)

"foo" is the id of the dynamic image on the HomePage, NotFoundPage is the 404 page. It seems wicket is mixing up the component hierarchy and the markup in this case.