- auditing <= outside NH scope. There are various interpretations of what mean "auditing". In the NH3 cookbook you have 3 solutions without need to add external references. Simon and Roger are working on the port of Envers that is another interpretation about what mean "auditing".
- validation <= outside NH scope and, btw, you have at least others 4 frameworks we the specific responsibility of validate objects. DataAnnotations, VAB, Castle, Spring, FluentValidation and so on. Validation is a cross cutting concern, NH give you the ability to inject the validation of your objects before persist it (on Save, update.... or just before flush the session). - INotifyPropertyChanged <= I have no idea about what mean to give support to INotifyPropertyChanged. NH is not a code-generator to generate entities. If your entities implements INotifyPropertyChanged for NH there is no problem. If, in your opinion, you can take some advantage implementing INotifyPropertyChanged you can do it with less than 50 code lines: http://fabiomaulo.blogspot.com/2010/10/turbo-nhibernate-with-domain-invaders.html - security <= I'm inclined to say that again it is outside NH scope but I would understand which kind of "security" you are talking about. On Thu, Oct 14, 2010 at 2:19 PM, Frans Bouma <[email protected]> wrote: > 1st: I'd like to state that if I post here, I don't like it when I see what > I posted questioned on twitter. if you have questions, ask them in a reply > > 2nd: I meant: if I want for example: > - auditing, > - validation > - INotifyPropertyChanged > - security > > in my application which uses NH, I'd like to do that with e.g. > configuration > elements in the config file, and not having to worry whether I have the > latest nightly build of a 0.x versioned lib tucked away in some dark corner > of sourceforge: that's bad because: > 1) what if the lib gets abandoned in a year? Will I still be able to > maintain my app? > 2) what happens if I update NH because of a bugfix release? > > FB > > > On Thu, Oct 14, 2010 at 1:18 PM, Frans Bouma <[email protected]> wrote: > > > > > > - all functionality needed in 1 box, so you can focus on what > you're > > payed > > to do. > > > > > > > > the last one is not the definition of toolkit, here we call it as > > "masacote". > > To have all "functionalities needed" (and here I would know the > definition > > of "needed where and to do what") in all places/applications where NH is > > used, more than 1 box we need a truck. > > > > -- > > Fabio Maulo > > > > > -- Fabio Maulo
