| Re: [ee4j-community] Eclipse Jetty and EE4J |
Thank you, Jetty team, for showing such support for the new EE4J community. It's great to see that the former JavaEE effort found a great and welcoming home at Eclipse foundation. Having no RIs is an interesting idea, I would still recommend to have RIs for now. MicroProfile project is exploring the path without any RIs and if goes well, the EE4J community can also adopt it later. Regarding Servlet spec, Glassfish is the RI now. As a Payara engineer, I know Glassfish servlet engine is based on a fork of an older version of Tomcat, which uses Grizzly NIO as the HTTP engine. This causes problems as it's hard to keep the fork updated. I can imagine that a future version of Glassfish is bases on Jetty instead. While Glassfish could remain an RI for Servlet spec, I believe a close collaboration with the Jetty team would be beneficial for everybody. Ondro Od: Werner Keil Not being a Standard, MP can afford to go without a RI. Some sub projects create "Sample Implementations" while others leave that completely to a particular vendor. I think there should be a little more consistency on that. Jetty is a compatible Servlet Implementation but not the RI. Whether it could play such role under EE4J guess you have to discuss that with the respective people when the time comes. Unlike Glassfish it certainly could be an advantage having moved all Code to Eclipse already. Servlet JSR needs a RI if it was continued under javax.servlet. The only way not to have a RI would be to break entirely with the existing Servlet Standard and create a new one in a different place. Werner |