[forge-dev] Data access logic used by scaffold code

[Dan Allen]

On Tue, Jan 24, 2012 at 18:15, Rafael Pestano <rmpestano at gmail.com> wrote:

> Hi everyone,
>
> its not just a matter of using different ScaffoldProviders in
> generateFromEntity plugin?
>
> if you want vanilla javaEE code generation use FacesScaffold, if you want
> CDI Quey use CDIQueryBasedScafold and so on...
>
> or its not that simple?
>

It's true. And from the conversation above, it looks like that's where we
are headed.

I say that because:

(a) it appears the Java EE purist output is an immovable requirement
(b) we definitely want to offer output that *does* use a framework for
those that want it (CDI Query likely)

Now, if at some point we decide that (b) isn't needed anymore, then (b)
because the preferred recommendation. Yeah.

Granted, (a) and (b) won't be all that different, so we certainly aren't
dumping work. (b) is simply introducing a dependency that effectively trims
down what (a) produces.

I think Jason should proceed with what the (b) output will look like for
the Open18 migration, then we can work it back into a (b) plugin.

-Dan

-- 
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20120124/89b21171/attachment.html