IIRC, there were two requirements: 1. Auto-properties; 2. Castle proxy (i.e., it wasn’t implemented for LinFu or Spring).
The 3.1 proxy implementations are now obsolete (as documented in the release notes), but I suspect that if this worked in 3.1 then this should be raised as a JIRA. From: Joakim Gran Sent: Thursday, May 10, 2012 8:43 PM To: [email protected] Subject: Re: [nhibernate-development] Lazy properties -> anemic entities? I'm definitely using auto properties to define my lazy property. Even if I make the property public my entity method won't trigger any load. Can someone just tell me if this is a bug or if it is "as designed"? If it is as designed I'm sure it is for a good reason and I will just go ahead and refactor my domain and move the lazy properties into real lazy loaded child entities. But this is a breaking change since version 3.1 that I didn't see documented anywhere. A warning should also be made that using lazy properties will effectively turn your entites into dto:s. /Joakim
