I think that my comment sounded a little bit extreme and I'd like to rectify
my viewpoint a little bit.
I don't know if you guys share my vision, but I think that's "extends
genericLayer<T>" e.g. is very invasive. But of course if we can't come out
with a better way out of it using annotations, generic beans, decorators or
etc... It's an acceptable solution. We're dealing with it for the last 5
years already.
On Tue, Sep 20, 2011 at 5:00 PM, José Rodolfo Freitas <
joserodolfo.freitas(a)gmail.com> wrote:
Yeah, I agree that being declarative is the ideal.
let's say no to inheritance with generics! hehehe.
On Tue, Sep 20, 2011 at 4:41 PM, Dan Allen <dan.j.allen(a)gmail.com> wrote:
> On Tue, Sep 20, 2011 at 15:36, José Rodolfo Freitas <
> joserodolfo.freitas(a)gmail.com> wrote:
>
>> What I like most in CDI and Seam3 is that it's very easy to keep things
>> simple and that's something I strongly advocate.
>
>
> +1
>
>
>> Of course there're still boilerplate code, but I think it's minimal
>> (compared to the JEE generations before), and that's something forge can
>> create without the need to satisfy a "framework". Yes, I admitedly am
afraid
>> of that word.
>>
>
> That's fine, it doesn't have to be a framework. I do think there is room
> for having some common scaffolding, though. If we can do that by extending
> the programming model (annotations, generic beans or interfaces) so that
> it's declarative, that's probably ideal.
>
> I suggest that we brainstorm proposals using gists (
>
http://gist.github.com). That will get the ball rolling. We can start
> with the idea Jason posted, or feel free to take a different approach.
>
> -Dan
>
> --
> Dan Allen
> Principal Software Engineer, Red Hat | Author of Seam in Action
> Registered Linux User #231597
>
>
http://www.google.com/profiles/dan.j.allen#about
>
http://mojavelinux.com
>
http://mojavelinux.com/seaminaction
>
>