Two problems: 1) It only works when talking about data from one entity. What if my query went across several entities / tables, retrieving some attributes from each? Can't use a ejbFinder. And because ejbSelect statements can only return one result per row, they don't work either.
2) this declarative approach at build time forces the read-ahead strategy on all users of the bean, whether their transactions require it or not. Making it impossible to allow optimal performance per transaction. The problem is that ejb querying is an insufficient API. At the moment I really feel this is broken by design, and that another solution such as Hibernate has to be used. Please point out why I'm wrong. I would love not to be forced to convert all the entity bean code we have developed over the past year to Hibernate. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862087#3862087 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862087 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
