|Re: [equinox-dev] equinox http service|
I think we should target Java 6 if it makes life more simple. Our jetty backed solution on Jetty 8 already requires Java 6 and I have been told that Servlet 3.0 requires Java 6 as a minimum. Moving forward we need to figure out if we can pull off a base http.servlet bundle that supports 3.1 and 3.0 servlet. I think Servlet 3.1 may require Java 7, but in the past we have been able to have http.servlet support much older Java versions.
BTW, I would like us to consider having the http.servlet bundle be as forwards compatible as possible. I think this is important for cases where a war is delivered with http.servlet bundle embedded. Otherwise the bridge style WAR will become incompatible on later servers that implement the very latest servlet spec.
Currently we attempt to do this by using proxies for provider types like the ServletContext which then delegate to the hosting container's provider type implementations.
Raymond Auge ---03/23/2014 10:05:16 PM---With respect to updating org.eclipse.equinox.http.servlet to RFC 189. Are we increasing:
From: Raymond Auge <raymond.auge@xxxxxxxxxxx>
To: Equinox development mailing list <equinox-dev@xxxxxxxxxxx>,
Date: 03/23/2014 10:05 PM
Subject: Re: [equinox-dev] equinox http service
Sent by: equinox-dev-bounces@xxxxxxxxxxx
On Mar 21, 2014 5:26 PM, "Raymond Auge" <raymond.auge@xxxxxxxxxxx> wrote: