Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
New test: JSF #307
I doubt that a test for JSF would produce any meaningful data. The benchmark is focused on JSON serialization and database access. Both topics are completely beyond the scope of JSF. Being a component based framework, JSF does not return raw JSON, though responses to async requests may contain JSON.
A comparison between JSF implementations and libraries would be very interesting but the benchmarking framework is suited to compare platforms rather than MVC frameworks that are based on the same technological platform. What's the meaning of comparing database access in JSF, GWT and Spring MVC based applications when Hibernate is used in any case?
More sophisticated test methods are required to provide meaningful data for a comparison of JSF implementations and libraries.
@tasel Thanks. The apparent mismatch of intents for JSF and this project is why we left JSF (and GWT) out originally. Nevertheless, I have heard several JSF users ask us to include JSF, hence this issue.
I'm not a JSF developer, so I appreciate you confirming our earlier assumption that as long as we're testing fundamentals, it's quite difficult (and without much value) to shoehorn JSF into our test-cases.
I'm going to close this. We'd still accept a JSF implementation of the tests if someone were to create a pull request, but JSF users would probably be dissatisfied with the tests.
I think I could make a workaround to create such test, but it would have some overhead and it would not be very good for the benchmark. Is it possible to we create a different category of test which use tools like webdriver/selenium to get the metrics of such frameworks? I think people might like this new type.
While JSF doesn't fit for the JSON/Plaintext portions of the test the entire EE7 stack does cover all of it.
JAX-RS + JPA for the JSON, Plaintext, Single Query, Multiple Query, Updates tests.
JSF + JPA for the Fortunes test.
#755 is an initial implementation of this. Though we are wanting to wait until Wildfly hits Final before inclusion.