Hi community,

I was working on the Servlet, I I have been able to bring it down to
https://tck.work/tomee/tests?build=1607984842299&path=com.sun.ts.tests.servlet

22 remaining failures.

Based on Tomcat's following page
https://cwiki.apache.org/confluence/display/TOMCAT/Servlet+TCK+4.0

I added some excludes for tests which were fix because of known bugs
See
https://github.com/apache/tomee-tck/blob/master/src/test/resources/ts.jtx#L24

On the 22, we still have some pending tests as explained in the Tomcat wiki.
I haven't excluded them because they aren't flagged as bugs on the TCK, so
until the challenge is accepted and fixed, we should leave them in my
opinion.

I'm trying to get some of the permission fixed as well by adding the
security manager.


   - com.sun.ts.tests.servlet.spec.security.clientcert.Client (1
   failure)--> JDK issue fixed with 1.8u221 - I already updated the
   certificates because they were expired
   - com.sun.ts.tests.servlet.ee.spec.security.permissiondd.Client (14
   failures) --> We need the security manager with Tomcat
   - com.sun.ts.tests.servlet.ee.spec.security.runAs.Client (2 failures)
   --> we need a role mapping so user can switch from j2ee to javajoe. We do
   support role mapping but with openejb-jar.xml (not standard way - each
   container has its own). As the TCK provides Glassfish role mapping already,
   we should be able to easily pass this by just improving the SunConversion
   class to read and map the roles to our internal model.
   - com.sun.ts.tests.servlet.api.javax_servlet.srevent.URLClient (1
   failure)
   - com.sun.ts.tests.servlet.api.javax_servlet.asynccontext.URLClient (2
   failures)
   - com.sun.ts.tests.servlet.spec.security.secbasic.Client (2 failures)
   --> known. Under discussion

If someone wants to take the RunAs, it's an easy one to do. I can provide
some guidance.

--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com

Reply via email to