I'm also currently trying out hibernate / xdoclet and find it is a very promising combination. However, I'm not so sure if you can really get rid of value objects (or something similar) in a layered architecture. Using value objects can be a good choice if you want to cleanly decouple different layers of your architecture . I wonder if I should extend my value objects functionality to transparently handle lazily loaded relations (uninitialized collection? -> go and initialize before accessing it!). Any suggestions?
Advantage is that you use plain old java objects (
POJOs ) , which can be tranfered over the wire (if they are serializable) - and thus all the stuff with interfaces, DDs value objects and CMR just dissapears.
Cheers,
Roger
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
