12.1.0.beta1

[joakime]

Special Thanks to the following Eclipse Jetty community members

• @kohlschuetter (Dr. Christian Kohlschütter)

Changelog

• Client responses of HTTP conversations have mismatching request #13244 - Client responses of HTTP conversations have mismatching request
• Keep extracted query params as attribute for jetty-core #13242 - Keep extracted query params as attribute for jetty-core
• Fix NPE in HttpReceiver.responseSuccess() when that method is called more than once #13240 - Fix NPE in HttpReceiver.responseSuccess() when that method is called more than once
• Prevent cycles/stackoverflow in dump #13230 - Prevent cycles/stackoverflow in dump
• Support arbitrary Handlers and core webapp archives in core-deploy #13218 - Support arbitrary Handlers and core webapp archives in core-deploy
• Deployment of XML only with ServletContextHandler sets wrong baseResource #13217 - Deployment of XML only with ServletContextHandler sets wrong baseResource
• Port async cross context dispatch to ee11 #13214 - Port async cross context dispatch to ee11
• Review WebSocket ClientUpgradeRequest API for 12.1 #13213 - Review WebSocket ClientUpgradeRequest API for 12.1
• Improve InputStreamContentSource byte[] handling. #13206 - Improve InputStreamContentSource byte[] handling.
• Re-implemented StacklessLogging to be thread safe #13205 - Re-implemented StacklessLogging to be thread safe
• Download of large file may get stuck in an infinite loop (bug in IOResources.copy / Content.Source) #13196 - Download of large file may get stuck in an infinite loop (bug in IOResources.copy / Content.Source) (@kohlschuetter)
• Missing API to increase QueuedThreadPool maxThreads by leased threads + QoSHandler bug of exceeding maxRequestCount by 1 #13187 - Missing API to increase QueuedThreadPool maxThreads by leased threads + QoSHandler bug of exceeding maxRequestCount by 1
• Merge Jetty 12.1.x Support maven.offline property in jetty-start, to control of download of maven files from remote repos during --add-modules (#13147) #13186 - Merge Jetty 12.1.x Support maven.offline property in jetty-start, to control of download of maven files from remote repos during --add-modules (Support maven.offline property in jetty-start, to control of download of maven files from remote repos during --add-modules #13147)
• Reviewed HTTP/3 API to simplify the implementation. #13181 - Reviewed HTTP/3 API to simplify the implementation.
• Fix HTTP/3 behavior in case of client reset. #13179 - Fix HTTP/3 behavior in case of client reset.
• use real url as this can eventually be used by some tooling #13170 - use real url as this can eventually be used by some tooling
• ProxyServlet abort #13164 - ProxyServlet abort
• Force servlet4 demos to be build last, to have ee8 built last #13156 - Force servlet4 demos to be build last, to have ee8 built last
• Cross Context Dispatch with Async does not honor context #13144 - Cross Context Dispatch with Async does not honor context
• Surface received GOAWAY in HttpClient #13131 - Surface received GOAWAY in HttpClient
• Common Annotation Parser #13122 - Common Annotation Parser
• HTTP2 Server Error Handling is different than HTTP1 #13098 - HTTP2 Server Error Handling is different than HTTP1
• InvalidPathException instead of MalformedURLException after switching to jetty12 #13057 - InvalidPathException instead of MalformedURLException after switching to jetty12
• Review WebSocket flushers #13043 - Review WebSocket flushers
• Rework websocket FrameFlusher's expiration #13013 - Rework websocket FrameFlusher's expiration
• Use websocket over varying http protocols using a single client #12659 - Use websocket over varying http protocols using a single client
• Guard against NullPointerException in AnnotationParser #12453 - Guard against NullPointerException in AnnotationParser
• NPE on trying to read uri, headers or attributes from the original HttpServletRequest wrapped in UpgradeRequest on WebSocket server in Jetty 12 #11294 - NPE on trying to read uri, headers or attributes from the original HttpServletRequest wrapped in UpgradeRequest on WebSocket server in Jetty 12
• Jetty 12 - conditional headers handling for welcome files #9632 - Jetty 12 - conditional headers handling for welcome files
• Allow multiple authentication options for a web app #5442 - Allow multiple authentication options for a web app
• Document ThreadPoolBudget behavior #4493 - Document ThreadPoolBudget behavior

---

This discussion was created from the release 12.1.0.beta1.

[pzygielo]

I'm trying 12.1.0.beta3 but can't see discussion for that, so using this beta1 instead.

With 12.0.25 I was able to instruct
ee9-deploy to use jetty.deploy.monitoredDir=X,
ee8-deploy to use jetty.deploy.monitoredDir=Y,
ee10-deploy to use jetty.deploy.monitoredDir=Z.

I see that

1. with Change DeploymentScanner monitoredDir names to webappsDir #13104
   • monitoredDir no longer works, as replaced with webappsDir (let's say that's fine),
2. and - I also can't have multiple webappsDirs, as there is only one deployment-scanner which seems to work with single location.

Is there anything I could do to keep my different environment applications split?

[pzygielo]

Thanks for checking.

Please open an issue about this.
a fix in the current module

If I'm the only one, there is no need to rework that on jetty side, thank you.

(But if the Jetty Team decides to support multi-valued webappsDir, I will be happy to see that.)

this means you will still need to specify a *.properties file that configures the eeN environment for each web application

But of course. X-app.ee*properties are to stay.

I'll probably manage to prepare for current depolyment-scanner (one dir), before final 12.1 is ready (or delay upgrade a bit, depends).

[sbordet]

(But if the Jetty Team decides to support multi-valued webappsDir, I will be happy to see that.)

I think it's a good feature, and it's simple to implement, so yes please open an issue.

[pzygielo]

• Support multiple directories to be scanned by deployment-scanner #13472

[joakime]

Out of curiosity, why do you have multiple webapps directories?
What kind of thing is having multiple directories solving for you?

[pzygielo]

Out of curiosity, why do you have multiple webapps directories?

Inherited file system layout currently keeping ee8, ee9, ee10 separately.

What kind of thing is having multiple directories solving for you?

Not sure there was anything to solve.
I guess - this was possible to do, and hence it was done so 😄