Not all exceptions are properly handled by the WicketFilter -> results in empty response document with unset status code -> seen as HTTP_OK by client

Our custom ResourceStreamLocator might throw RuntimeExceptions.
When doing so, the exception handling of the WicketFilter doesnt properly handle this situation and creates an empty document with unset response code, which is usually sent to the client as HTTP_OK.

quickstart follows.