Jan Bartel
Jan Bartel
See #12528 ResponseTest
See #12529 ee9 BlockingTest
As I started saying over here: https://github.com/jetty/jetty.project/pull/13220/files#r2141231426 I think that: * `CoreContextHandler` should become `CoreAppContext` so it is symmetric with `WebAppContext` and we can naturally refer to `"core apps"` and...
See #12533 TestJettyJspServlet
See #12534 DefaultServletTest and ResourceServletTest
@sbordet not sure I follow what you're advocating. None of our existing session code uses `synchronized`, we do our own locking. If you're talking about apps needing to synchronize usage...
@sbordet well, I guess users of core sessions can cast the `Session` returned by `request.getSession(true)` to a `ManagedSession` and then use the existing `ManagedSession.lock()` method in a `try-with-resources` block to...
@sbordet adding a `getLock()` method to the `Session` api can be misleading to users: it's only useful iff you're using the `DefaultSessionCache` where session objects are shared. If you're using...
This issue appears to be addressed by the jersey project, so closing here also.
@basil interesting re-use of the jetty maven plugin! It's not doing the same thing twice: when `ServerSupport.configureDefaultConfigurationClasses(server)` is called, it is setting up the names of the configuration classes that...