The following function call always returns with true:
However, async calls fail even if the webconsole plugin tries to provide some resource (with some special extension on the end of the URI).
In the end of the OSGiManager.service(ServletRequest, ServletResponse) function, there is the following:
Due to the reason that flushBuffer() function is called, any asynchronous handling will fail with an exception.
- In case the webconsole plugin is rendered (the path ends with / or .html), the request.isAsyncSupported() method call should return false
- In case a custom resource is provided by the webconsole plugin (any extension but html on the end of the path) the flushBuffer() method should not be called
At least the second part of the fix should be implemented as if a plugin wants to provide bigger files (like a dump), async support can be useful. Also, by the time more and more libraries will support asynchronous IO to provide resources and if a webconsole plugin uses such library, it will fail.