Just one wish: I like the search order idea, it makes it easier to use.
But we should also have the possibility to specify the strategy very explicitly for each class and even property.
Yes, I agreed.
But for now I going to develop a more simple solution (and I believe it would satisfy 80% of developers), and then, me or another person will add fine-grained control over which classes use which persistence mechanizm.
It's because I'm very loaded with other open-source projects and I need only _this_ kind of functionality. If I'll have time, I'll do more, if not -- I will not, leaving it for others. It's how the open-source works, right? ;)
dozen
------------------------------------------------------- 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/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
