I have put together an initial draft of the persistence module page [1]. I&#39;ve outlined the major issues that this module needs to address along with some rough design notes. The next step is to identify what features to tackle first by sketching out a roadmap (alpha1, alpha2, etc with bullets next to them). I&#39;ll take the first stab at it.<div>
<br></div><div><div>- If you are a current Seam committer interested in helping with this module, please add your name to the table and feel free to revise or add to the design notes.</div><div>- If you are not a Seam committer, you can start by helping with the design notes and we can work you up to committer status as you demonstrate commitment and expertise.</div>
<div><br></div><div>Like the security module, the persistence module is very important because it fills a gap that still exists in Java EE (transactions for non-EJB managed beans). Developers are mostly likely going to need this module to write an app, primarily if they are trying to avoid using EJBs. I still believe that we should advocate EJB 3.1, though, despite working on this module. We could consider it a half-way house for people who have been burned by EJB in the past :)</div>
<div><br></div><div>-Dan</div><div><br><div>[1 <a href="http://seamframework.org/Seam3/PersistenceModule">http://seamframework.org/Seam3/PersistenceModule</a></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>

</div></div></div>