I understand your point better now in case of using Hibernate directly. Yet with EJB3 this should not present a problem, in particular not the way it currently does. I would much rather incure the overhead on the database and in the persistence layer, then have duplicate objects returned. Also having been given all this new functionality by EJB3 I would hate to base my object graph design on the limitations of the underlying persistence framework.
Is there a better way to annotate the entities, so that they are not loaded in the same fetch operation ? I think that would really solve my problem. A brief example would even be better. Thanks Alex View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3923468#3923468 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3923468 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
