Agreed but having logging code mixed with business logic surely cannot be ideal.
In relation to logging in the middle of a method, is it not a code smell anyway? Could that method be "broken down" into smaller methods thereby giving an architecture that would enable you to log exactly what you want? Also, is there a valid argument the simplify logging in NHibernate, thereby enabling an AOP framework to cater for logging requirements. - Disadvantage: Less logging - Advantage: Cleaner code base + the likes of NHibernate profiler etc are now available to help with issues On Fri, Jul 10, 2009 at 3:11 PM, Tuna Toksoz <[email protected]> wrote: > NHibernate doesn't only log exceptional cases, you can't do aop in the > middle of a method. > > Tuna Toksöz > Eternal sunshine of the open source mind. > > http://devlicio.us/blogs/tuna_toksoz > http://tunatoksoz.com > http://twitter.com/tehlike > > > > > On Fri, Jul 10, 2009 at 5:09 PM, bstack <[email protected]> wrote: > >> using e.g. the likes of PostSharp? I know there are discussions going > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
