IMO, this problem is not really GWT related but standard hibernate/jpa behaviour. Either you define your relationships as lazy, which means that they are not loaded when the parent object is loaded, or you define the relations as eager fetch. The best practice is lazy load and then load the needed relationships on a adhoc basis using Hibernate.initialize(donor.getDonations()) to fetch them.
So you want the donations to come with the donor, initialize that relation during the transaction. Outside the transaction, any relation that was not loaded will throw a lazy load exception when you read any out of these related objects. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
