Hey Dan,<br><br>We can definitely look in to a scaffold-provider that uses an extension for query logic! We need to work on the extension points for the scaffold anyway, so that would be a good thing to do while we work on that. It&#39;s important to make sure we keep up a pure EE implementation at the same time as well, but Metawidget has proven excellent for many kinds of Generation, so I think that we should definitely consider that as a very good option for working on another provider :)<br>
<br>~Lincoln<br><br><br><div class="gmail_quote">On Tue, Jan 24, 2012 at 1:11 AM, Dan Allen <span dir="ltr">&lt;<a href="mailto:dan.j.allen@gmail.com">dan.j.allen@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Richard and Jason,<div><br></div><div>Both of you are working on (polished) code to provide CRUD functionality in Java EE 6 / CDI, code that was laid down for Seam 2 applications by seam-gen. Namely, you are replacing the Home and Query components, Richard for the Forge scaffolding and Jason for migrating a seam-gen app to Java EE 6. </div>


<div><br></div><div>Ideally, you&#39;ll both reach the same endpoint. By that, I mean that the CRUD architecture in a new Forge application should match the code that we recommend for developers migrating from Seam 2 (specifically seam-gen apps). Otherwise, developers are going to be stuck trying to decide which direction to go...and that&#39;s no good obviously.</div>


<div><br></div><div>Richard, I noticed that you are taking the no framework route by using the EntityManager directly and weaving both CRUD, conversation and pagination in a single component. Are you fixed on doing it that way, or would you consider using something like the CDI Query extension developed by Thomas and Bartosz from CTP [1]?</div>


<div><br></div><div>I&#39;m not trying to push you guys in either direction, other than I hope that we can settle on a single approach to become the recommended way of doing CRUD. The Seam community has been asking for a CRUD and Query module for a looooooong time, and we are now at the point where we actually need it ourselves.</div>


<div><br></div><div>I&#39;m interested to hear your feedback, and anyone else that has opinions or ideas for that matter.</div><div><br></div><div>-Dan<br clear="all"><div><br></div><div>[1] <a href="http://ctpconsulting.github.com/query/1.0.0.Alpha2/index.html" target="_blank">http://ctpconsulting.github.com/query/1.0.0.Alpha2/index.html</a></div>
<span class="HOEnZb"><font color="#888888">

<div><br></div>-- <br><div>Dan Allen</div>Principal Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><div><a href="http://google.com/profiles/dan.j.allen" target="_blank">http://google.com/profiles/dan.j.allen</a><br>


<a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br></div><br>
</font></span></div>
<br>_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.com">http://ocpsoft.com</a><br><a href="http://scrumshark.com">http://scrumshark.com</a><br>&quot;Keep it Simple&quot;<br>