Stephan, since you're at the tests, I got one advice about the Jetty-TestClient (in case you havent found this yourself). If you set the debug-level to INFO or DEBUG, the TestClient will print all Responses to the console. This way it is much easier to compare the results or check for certain JSF-param-names like we just did.
regards Marc Am Freitag, 17. März 2017 11:08:26 UTC+1 schrieb Stephan Siano: > > Hi, > > to sum up the result: > > 1. Most of the adapted tests work as in Jetty (this means that they work > if they work with Jetty or don't works if they do not work in Jetty (as the > issue with PAXWEB-1078)). > 2. There are actually two open issues that cause tests that run in Jetty > to fail in Tomcat: PAXWEB-1079, and PAXWEB-597 > 3. One test does also not run in Tomcat > (WarJSFPrimefacesIntegrationTest.testPrimefacesTagRendering()), but I > actually do not understand the test case. > > Best regards > Stephan > -- -- ------------------ OPS4J - http://www.ops4j.org - ops4j@googlegroups.com --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to ops4j+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
