Thanks for coming up with TomEE. I read about TomEE, watched the video, got excited but felt disappointed working with it and JSF 2.0, Hibernate, MySql and Primefaces. It has been frustrating for me working with TomEE and JSF. Configuration
Initially, I thought you could drop a JSF war in TomEE without issues but that is not true. TomEE jars conflicts with jars in a jsf web application. TomEE expects all your jars to be in TomEE lib directory - which is awful and not a good design. Some configurations that are usually done in a web application, TomEE expects them to be done in tomee.xml. This will not scale if you have multiple applications deployed in TomEE. I noticed too that it is not easy to swap out MyFaces jars and use javax.myfaces jar. Also, any attempt to use javaee-api jar is a no no. I may be wrong in some of my assumptions and findings but a good way to go is for someone in the TomEE team to come up with a pure JSF 2.0 example that shows how: 1. To annotate the Managed bean 2. Create a service that fetches data from a MySQl database with a defined Entity bean 3. Show how to inject the service in a Managed bean 4. Show a .xhtml file that uses the Managed bean (use Primefaces as the add on component) 5.And Finally (very important) show the persistent.xml and what entries are required in web.xml and tomee.xml. Which jar files should be in the web lib directory and which one should be in TomEE lib directory? Don't point me to the examples, I have seen all of them. They are helpful but they did not solve the issues I raised. A really simple functional and complete JSF 2.0 example will help a great deal. Thanks. -- View this message in context: http://openejb.979440.n4.nabble.com/Running-TomEE-plus-jsf-Examples-Fails-tp4656561p4656564.html Sent from the OpenEJB User mailing list archive at Nabble.com.
