That's a good idea too Stuart. Can we easily make use of something similar for EntityHome, or do you think we have something easy enough with what I posted. 

Sent from my iPhone

On Sep 20, 2011, at 20:15, Stuart Douglas <stuart.w.douglas@gmail.com> wrote:

My original plan for EntityQuery was to use the ServiceHandler stuff in solder:

@EntityQuery
public interface MyQuery {

  @Query("Select u from User u where type=:p1")
  public List<User> users(String type);

}

Stuart

On 09/21/2011 06:00 AM, José Rodolfo Freitas 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@gmail.com> wrote:
On Tue, Sep 20, 2011 at 15:36, José Rodolfo Freitas <joserodolfo.freitas@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




_______________________________________________
seam-dev mailing list
seam-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
seam-dev mailing list
seam-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev