> -----Original Message----- > From: Adam Levine [mailto:[EMAIL PROTECTED] > Subject: RE: [Xdoclet-user] defining self-referring / recursive CMR > > <snip/> > It works, it's just not as clean as we'd like it to be. > Hence, the desire > for a depth read control.
There really isn't much concept of state in a template. It's one level (no aggregation), two levels (what I described) or infinite recursion (unbounded aggregation) in this case. It sounds like you've gone far enough with this to realize that. If you think you have some functionality that can improve the template for the few without slowing it down for the many, please don't hesitate to contribute! If it were me, I would subclass the generated VO and override the methods for looking up the aggregated CMR. The override class could have a field for the recursion depth that you could set through an accessor. There's nothing wrong or ugly about that, and it's a clean separation between the tool and the environment that should be robust as people make changes so long as the relation names don't change. best, -b ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
