RESTEasy > Blogs > RESTEasy 6.2.10.Final and 7.0.0.Alpha3 Releases

RESTEasy 6.2.10.Final and 7.0.0.Alpha3 Releases

By James R. Perkins | August 19, 2024

Today we’d like to announce the release of RESTEasy 6.2.10.Final and RESTEasy 7.0.0.Alpha3.

Both the 7.0.0.Alpha3 and 6.2.10.Final releases are bug fix and component upgrade releases.

7.0.0.Alpha3

RESTEasy 7.0.0.Alpha3 is a Jakarta REST 4.0 implementation.

Bugs

• RESTEASY-3500 - The ExceptionHandler sets the media type of an exception to text/html
• RESTEASY-3510 - Default ExceptionMapper cannot be disabled by setting “dev.resteasy.exception.mapper” to false through in web.xml
• RESTEASY-3515 - By default the REST Client implementation should use SSLContext.getDefault()
• RESTEASY-3520 - ArrayIndexOutOfBoundsException when using eclipsemicroprofile REST client with custom ContextResolver
• RESTEASY-3531 - If jetty-utils is on the class path, resteasy-undertow-cdi will fail to process requests
• RESTEASY-3532 - RESTEasy Jetty Client does not add boundary for multpart requests on the content-type header

6.2.10.Final

RESTEasy 6.2.10.Final is a Jakarta REST 3.1 implementation.

Bugs:

• RESTEASY-3510 - Default ExceptionMapper cannot be disabled by setting “dev.resteasy.exception.mapper” to false through in web.xml
• RESTEASY-3515 - By default the REST Client implementation should use SSLContext.getDefault()
• RESTEASY-3520 - ArrayIndexOutOfBoundsException when using eclipsemicroprofile REST client with custom ContextResolver
• RESTEASY-3531 - If jetty-utils is on the class path, resteasy-undertow-cdi will fail to process requests
• RESTEASY-3532 - RESTEasy Jetty Client does not add boundary for multpart requests on the content-type header

Finally

As always, feedback is welcome. Stay safe, and, depending on where you are, stay warm or be cool.