Hmm,
Spec says:
public boolean isAsyncStarted() - Returns true if async processing
has started on this request, and false otherwise. If this request has
been
dispatched using one of the AsyncContext.dispatch methods since it was
put in asynchronous mode, or a call to AsynContext.complete is made,
this
method returns false.
===
But the example with Bug 49528 don't call directly dispatch, it calls
AsyncContext.start().
At Tomcat we start doesn't start a Container Thread. We internally
call a doInternalDispatch at StandardWrapperValve
with the callee thread.
...
} else {
if (request.isAsyncDispatching()) {
//TODO SERVLET3 - async
((AsyncContextImpl)request.getAsyncContext()).doInternalDispatch();
...
I revert the fix, and correct the testcase.
Peter
Am 04.07.2010 um 21:23 schrieb Rainer Jung:
On 01.07.2010 18:42, Rainer Jung wrote:
On 01.07.2010 17:20, Marc Guillemot wrote:
jean-frederic clere wrote:
...
I run a daily test and just looked to what breaks it and complain.
Now I am looking to Peter's application to find what is broken.
so you're the continuous integration server ;-)
Can you publish break information or is it forbidden by the TCK
license/agreement?
Exact details are forbidden, but I'm sure there'll be some
information
The symptom is: it breaks
"If this request has been dispatched using one of the
AsyncContext.dispatch methods since it was put in asynchronous mode,
this method returns false."
which is part of the spec description of "public boolean
isAsyncStarted()".
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
