On Jan 11, 2011, at 2:34 PM, Thomas Heute wrote:
As you may know, WCI has evolved to support Servlet 3.0. It will come in
WCI 2.1
Tomcat 7.0 and Jetty ??? should be now supported by WCI and JBoss 6.0 is
coming.
Jetty 6.1 for the moment, we haven't yet given a look at Jetty 7 (Servlet 3.0)
WCI 2.0 used to be tested before release against:
- JBoss 4.2
- JBoss 5.1
- Tomcat 6
I propose that we drop testing JBoss 4.2 (for simplicity and since we
won't propose GateIn packaged with JBoss 4.2) and "only" test for WCI 2.1:
- JBoss 5.1
- JBoss 6.0
- Tomcat 6.0
- Tomcat 7.0
- Jetty ???
I agree with you, however pruning JBoss 4.2 is just a matter of removing build
complexity.
Please let me know if that's an issue. Also since I haven't checked, I
would like to know about the tested Jetty environment.
I haven't tested myself yet but I am about to do it as I'm going to test the
portlet container with it.
I have been working recently a bit on PC update, for now improving the build to be simpler
and remove redundancy. It's based on Matt's effort done in WCI with a few
improvements.
According to Alain, some tests are not passing for Jetty in PC and I need to look at it,
with several possible outcomes:
1/ Jetty is not compliant 100% to servlet spec
2/ Tomcat (and therefore Tomcat based containers) is not 100% compliant and the PC is
designed to work around it
3/ Both are not compliant :-)
4/ Both are compliant but the PC does not use correctly the servlet spec
I will keep you informed about my investigations.
Thomas.
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev