Mark Thomas
Mark Thomas
> Is the existing [`servlet-dev`](https://accounts.eclipse.org/mailing-list/servlet-dev) mailing list just for committers on this project? I think that is a decision the Servlet community can make (and not one that has been...
This has been handled as part of the fix for #443.
I agree that that date should be acceptable. That it isn't makes this challenge valid. I am wondering how containers have passed the TCK. Something to look into but doesn't...
Closing this issue as this has been addressed in the refactored TCK for Servlet 6.1. Tomcat uses the `Wed, 12 Oct 2022 15:18:45 GMT` format and passes the TCK.
I don't think we had consensus. My expectation is that RequestDispatcher is going to have to decode the path. My reasoning is: - the servlet spec says that path can...
Fixed by #580
You have re-opened the wrong issue. That text was only reformatted by the fix to this issue. The original change was made to address #18.
I don't see a reason for `onError()` to depend on whether `isReady()` has been called. `onError()` should be triggered as early as practical. I'd expect `isReady()` to return `false` once...
For that specific instance I think I'd expect the exception on the AL with the WL and RL only seeing exceptions if further write/reads are attempted. ie treat it in...
I like a lot of this latest description. A couple of minor comments. In Tomcat, an IOException during `SIS.isReady` will cause `isReady` to return false and `RL.onError` to be called....