hi, A public API for initiating an upgrade at runtime was removed [1] which breaks WebSocket support in the Spring Framework. This API was previously added to make up for a limitation in JSR-356. The hope was for it to be picked up in a spec update but unfortunately there has been no movement whatsoever on that front. For what it's worth an identical API has been added to several other Servlet containers.
Rossen [1] https://github.com/apache/tomcat/commit/fe72ea5deb57d7eedf00387c1d79049ca64681ee [2] https://java.net/jira/browse/WEBSOCKET_SPEC-211 On Thu, Mar 17, 2016 at 4:00 PM, Mark Thomas <ma...@apache.org> wrote: > The proposed Apache Tomcat 8.5.0 release is now available for voting. > > This is the first release of the 8.5.x branch. The release is, in essence: > - Based on a copy of the 9.0.0.M4 tag > - All 9.0.x changes to the specification APIs have been reverted. The > specification APIs should match 8.0.x exactly > - Java 8 specific code has been re-written for Java 7 > - Tomcat and specification versions have been set > > It can be obtained from: > https://dist.apache.org/repos/dist/dev/tomcat/tomcat-8/v8.5.0/ > The Maven staging repo is: > https://repository.apache.org/content/repositories/orgapachetomcat-1066/ > The svn tag is: > http://svn.apache.org/repos/asf/tomcat/tc8.5.x/tags/TOMCAT_8_5_0/ > > The proposed 8.5.0 release is: > [ ] Broken - do not release > [ ] Alpha - go ahead and release as 8.5.0 > [ ] Beta - go ahead and release as 8.5.0 > [ ] Stable - go ahead and release as 8.5.0 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > >
