You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the currently active Servlet invocation was obtained by a call to AsyncContext.dispatch(), the returned HttpServletMapping is the one corresponding to the path that caused the first Servlet in the invocation sequence to be invoked.
The current implementation violates this proviso. It currently returns the mapping corresponding to the last Servlet in the invocation sequence.
The text was updated successfully, but these errors were encountered:
Turns out the initial values and behaviour were right after all, but the javadoc and therefor the TCK assertion was wrong. This was rectified in jakartaee/servlet#377 and therefor this issue needs to be reverted for GF 7.
This issue has been marked as inactive and old and will be closed in 7 days if there is no further activity. If you want the issue to remain open please add a comment
HttpServletRequest.getHttpServletMapping() states:
The current implementation violates this proviso. It currently returns the mapping corresponding to the last Servlet in the invocation sequence.
The text was updated successfully, but these errors were encountered: