On Aug 15, 2013, at 5:47 PM, Mark Thomas wrote: > This isn't going to be quite as simple as I first thought. > > The WebSocket client API requires Java SE 7 or later. > The WebSocket server API requires Java EE 6 or later. > Java EE 6 requires Java 6 or later. > The WebSocket server API depends on the WebSocket client API. > > The WebSocket client implementation makes extensive use of new Java 7 > non-blocking IO features. > > My conclusion from the above is that the back-port is going to require > Java 7. That begs the question how to do that while keeping the main > build Java 6 based. > > My (untested) plan is as follows: > - Create a WebSocket module > - Back-port (i.e. copy) the trunk code to that module > - Build just that module with Java 7 > - Make the minimum changes necessary to get it to work > - Modify the back-ported SCI so it only adds the filter if Java 7 is > detected (going to need to ensure the SCI is executable on Java 6) > - Ship Tomcat 7 with the WebSocket JARs > > Comments?
Sounds workable. Not ideal. But workable. Getting the SCI compiled to be executable shouldn't be a problem. Just compile the module -source 1.6 -target 1.6 on Java 7. As long as you don't use Java 7 language features, you can still compile against the APIs. Nick --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
