I made a small test, modifying the validation routine to explicitly let private setters slip through, and it seems to work just fine. Object hydrating etc. already handles this well. It's the validation routine which is a bit to simplified, as far as I can tell.
/G 2012/2/16 John Davidson <[email protected]> > One way is to comment here, but better yet is to vote on the jira issue, > and the best is to provide a proposed patch that passes all tests. > > John Davidson > > > On Thu, Feb 16, 2012 at 4:22 PM, Tom Bushell <[email protected]> wrote: > >> How do we go about raising their awareness? >> >> -Tom >> >> On Feb 15, 11:11 pm, Joseph Lam <[email protected]> wrote: >> > I'm also stuck at 3.1 due to a problem with NH proxy polymorphism. >> > Looking at the JIRA history and 3.3 road map the NH team seems to be >> > focusing mostly on LINQ stuff, and none of the outstanding issues >> > filed against the bytecode provider are assigned. I think it's worth >> > raising the awareness in the NH team about the seriousness of this >> > situation. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "nhusers" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/nhusers?hl=en. >> >> > -- > You received this message because you are subscribed to the Google Groups > "nhusers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/nhusers?hl=en. > -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
