Hi Ilia,
thanks for your request - see WICKET-6621
Have fun
Sven
Am 08.12.18 um 07:35 schrieb Илья Нарыжный:
Hello,
According to source code, it seems not possible to replace current handler
by 'null' - assuming that wicket in this case will allow web-server to
handle request further.
That's a code of wicket filter:
if (requestCycle.processRequestAndDetach())
{
webResponse.flush();
}
else
{
...
}
and here no way to fallback to default handling if at least one handler was
initially found:
public boolean processRequest()
{
try
{
set(this);
listeners.onBeginRequest(this);
onBeginRequest();
IRequestHandler handler = resolveRequestHandler();
if (handler == null)
{
// Did not find any suitable handler, thus not executing the request
log.debug(
"No suitable handler found for URL {}, falling back to container to process
this request",
request.getUrl());
}
else
{
execute(handler);
return true;
}
}
Please consider ability to fallback to default web-app handling of after
set of attempts to find proper handler system can't find out proper handler.
Thanks,
Ilia
---------------------------------------------
Orienteer(http://orienteer.org) - open source Business Application Platform
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
