Who said that is is gonna change ?What I said is that we will expose events as .NET events... with full backdraw compatibility. The advantage to have listeners as classes is clear... you can override some methods ;)
2009/2/15 CassioT <[email protected]> > > Hi Fabio. I extend IInterceptor, now you're talking about extend > DefaultSaveEventListener and you're saying that it's gonna change in > the future. What is you sugestion? Should I keep using IInterceptor, > change to DefaultSaveEventListener or wait for the new .NET like > event? Is there any pro's and con't between them? > > Thank you > > On Feb 15, 9:40 am, Fabio Maulo <[email protected]> wrote: > > 2009/2/15 Tuna Toksoz <[email protected]> > > > > > Oh i guess it is java style event listening. > > > > Not only that... > > The final result is similar to multi-cast-delegate using classes you can: > > 1) configure delegates outside the app code > > 2) Listeners has the same life cycle of SessionFactory > > 2a) Listeners can be initialized by SessionFactory during > > BuildSessionFactory > > 2b) Listeners can be statefull > > 3) As you can see looking at Default listeners, enclose a listener to a > > simple .NET delegate concept (one method execution) it is not so > > easy...inside Default-listeners you can find the heart of NH ;) > > > > BTW, in some moment, we will expose Events as .NET events. > > > > -- > > Fabio Maulo > > > -- Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
