<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
As to what Dan is referring to, it is likely JOTM:<br>
<a href="http://jotm.objectweb.org" target="_blank">http://jotm.objectweb.org</a>, which you won't have to deal with whether you<br>
are using an embedded EJB Lite container or a CDI specific transaction<br>
manager with JPA on Tomcat.<br></blockquote><div><br>Correct. I've also tried Atomikos Essentials, which I actually did get to work, but should everyone have to fill out a form to use transactions? <a href="http://www.atomikos.com/Main/TransactionsEssentialsDownloadForm">http://www.atomikos.com/Main/TransactionsEssentialsDownloadForm</a> That strengthens Gavin's point about how screwed up this situation with transactions has become.<br>
<br>What we we need a simple, reliable, documented way for developers to educate Tomcat how to do transactions correctly. I'm praying that EJB lite is that solution. I've heard some promising statements and we want to confirm them through our archetypes. The whole idea of creating these archetypes, as Steven said, is to get the developer using CDI, JSF 2, JPA and JTA without even a moment of time wasted, with their choice of Tomcat, Jetty or a Java EE container. When we have that, we will have accomplished our first, and most critical, goal.<br>
<br>-Dan<br></div></div><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>