On Sep 16, 2011, at 2:12 AM, Romain Manni-Bucau wrote: > Well we worked and work a lot for TCKs but we probably introduced a bug: if > we use normal tomcat deployement (and not remote one) a lot of work is not > done and some javaee6 functionnalities are missing. > > i think the magic should be done here: > org.apache.openejb.tomcat.catalina.TomcatWebAppBuilder#deployWebApps
Not sure if that will do the trick completely. Definitely something we'll want to fix (as best we can) before final release. We sort of have two integrations. One where Tomcat has already started deployment and notifies us and we have to do what we can at that later stage. This is the scenario where a webapp is dropped into the webapps/ dir. Then the other were OpenEJB starts the deployment and hands "webapps" to Tomcat. This is the scenario where someone drops an ear or jar into the webapps/ dir *or* if the command line deploy tool (or tck deployer) is used. The TCK setup currently only tests with the deploy tool scenario. We'll want to test both ways eventually. On my personal list of things to do post-certification: - Get a "deployment via webapps/ dir" tck setup working - Fix the Tomcat 6x support Probably in that order too. -David
