> > I already tried that and the log files got huge, > and the memory was > > crippled because the application server got stuck > in a loop going back > > and forth between the 2 same entities > > > Value Objects currently have a little(?) deficiency > in which they can't > be used in a circular way. So, if you have > aggregate/composed addresses > in your Employee value object, *don't* add an > aggregate/composed > employee in your Address value object. > > We've discussed this situation for a while, but it's > still without > solution. Any suggestions and patches are surely > welcome. > > -- > MB
Hi, What are other people doing to overcome/work-around this? I'm auto-generating my beans so it means that I could only safely choose 1 side of the relationship - so for instance I could choose the One2Many side and not generated the Value Object for the Many2One side; this would also mean I wouldn't be able to do any side for a Many2Many relationship (as I wouldn't know which side to pick). I'm assuming that use of Value Objects is common enough, and relationships are obviously common - so I would be surprised if people hadn't already developed work-arounds. If not then I don't think I can use Value Objects after all, which would be a terrible shame. Thanks Charlene __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com ------------------------------------------------------- This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
