I think that my comment sounded a little bit extreme and I'd like to rectify my viewpoint a little bit.<div>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.</div>
<div><br></div><div><div><div><div class="gmail_quote">On Tue, Sep 20, 2011 at 5:00 PM, José Rodolfo Freitas <span dir="ltr"><<a href="mailto:joserodolfo.freitas@gmail.com">joserodolfo.freitas@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Yeah, I agree that being declarative is the ideal.<div>let's say no to inheritance with generics! hehehe.<div><div>
</div><div class="h5"><br><br><div class="gmail_quote">On Tue, Sep 20, 2011 at 4:41 PM, Dan Allen <span dir="ltr"><<a href="mailto:dan.j.allen@gmail.com" target="_blank">dan.j.allen@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On Tue, Sep 20, 2011 at 15:36, José Rodolfo Freitas <span dir="ltr"><<a href="mailto:joserodolfo.freitas@gmail.com" target="_blank">joserodolfo.freitas@gmail.com</a>></span> wrote:<br>
</div><div class="gmail_quote"><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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. </blockquote><div><br></div></div><div>+1</div><div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>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.</div>
</blockquote><div><br></div></div><div>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.</div>
<div><br></div><div>I suggest that we brainstorm proposals using gists (<a href="http://gist.github.com" target="_blank">http://gist.github.com</a>). That will get the ball rolling. We can start with the idea Jason posted, or feel free to take a different approach.</div>
<div><br></div><font color="#888888"><div>-Dan</div><div><br></div></font></div><div><div></div><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://www.google.com/profiles/dan.j.allen#about" target="_blank">http://www.google.com/profiles/dan.j.allen#about</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>
</div></div></blockquote></div><br></div></div></div>
</blockquote></div><br></div></div></div>