On 25/02/2011 19:38, Christopher Schultz wrote: > Where does this fail the TCK? Do we have a broken Filter, or does the > TCK test an unusual/stupid scenario?
I am afraid I can't be more specific about this, the TCK is protected by an NDA. For that reason, I deliberately simplified my example to address the root cause rather than what the TCK is actually testing. Specific TCK discussions are held on the private mailing list. BTW, as a committer if you want access to the TCK, you just need to sign and submit the NDA. >> Thoughts? I'd like to reach some conclusions fairly speedily as this >> might hold up a 7.0.9 release. If we conclude that the filter is at >> fault in point 3, we'll need to raise a TCK challenge. > > I guess that answers my question. > > We could have a "just-pass-the-damned-TCK" configuration flag (or maybe > something less inflammatory) that would change this behavior to > commit-on-write for Filters. We could, but if the consensus is that the TCK is wrong (and so far it seems to be ) I'd be happy releasing Tomcat with a "we pass the TCK apart from an undisclosed number of tests we are currently challenging". Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
