7:27 a.m.
Hey Dan, you're about an hour late to the party :) we've been discussing and
Eichard has given me some info and code to look at and read through.
As for the non dep idea, I can certainly understand where Lincoln and Pete are coming
from. I do wonder though if that would preclude us from creating a CDI extension for
rolling our own simple CRUD framework perhaps with an spi for future expansion. That be a
bit much though. At any rate I need to go through the stuff Richard has sent me and give
some feedback.
Sent from my iPhone
On Jan 23, 2012, at 23:20, Richard Kennard <richard(a)kennardconsulting.com> wrote:
Hi Dan,
No, I'm not fixed. I am completely open to a CDI Query-based scaffold. And I agree
this is something that Seam (actually, Java EE) has been lacking for a
long time!
However the brief I was given was to generate a pure EE app with minimal (ideally zero)
non-EE library dependencies. Lincoln/Pete felt this was important,
at least for the default scaffolding provider. But this may have changed?
Regards,
Richard.
On 24/01/2012 5:11 PM, Dan Allen wrote:
> Richard and Jason,
>
> 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.
>
> Ideally, you'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's no good obviously.
>
> 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]?
>
> I'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.
>
> I'm interested to hear your feedback, and anyone else that has opinions or ideas
for that matter.
>
> -Dan
>
> [1] http://ctpconsulting.github.com/query/1.0.0.Alpha2/index.html
>
> --
> Dan Allen
> Principal Software Engineer, Red Hat | Author of Seam in Action
> Registered Linux User #231597
>
> http://google.com/profiles/dan.j.allen
> http://mojavelinux.com
> http://mojavelinux.com/seaminaction
>
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev