From: Ricardo P. (JIRA) <nh...@gm...> - 2011-04-11 11:42:08
|
[ http://216.121.112.228/browse/NH-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20884#action_20884 ] Ricardo Peres commented on NH-2638: ----------------------------------- Fabio, There is no difference. The mapping by code is working well. That is not the problem, you have done an excellent job in that. The problem I am having seems to me related with lazy entities. NH-2639 is the same, I think. If you have time, and interest, please check my demo project: http://cid-0450c015fc418de2.office.live.com/self.aspx/.Public/NHTest.zip. I may be doing something wrong, but I don't think so... I have always (since .NET 3.5, that is) used auto properties, even for ids, and I never had this problem. It is not critical to me, so if you have more urgent things do do, it's fine by me! I only wished I had confirmation from someone else that there is a problem. Thanks! > Id Property With Private Setter Not Set With Lazy Classes > --------------------------------------------------------- > > Key: NH-2638 > URL: http://216.121.112.228/browse/NH-2638 > Project: NHibernate > Issue Type: Bug > Components: Core > Affects Versions: 3.2.0Alpha1 > Reporter: Ricardo Peres > Attachments: Test.cs > > > When I have a class with a private id setter, if the class is lazy, then the id is not set. > No exception occurs, it simply is not set. Mapping is done with the new mapping by code. > Tested with the trunk version, as of 00:00. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://216.121.112.228/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |