recently, i blogged about an issue on NHibernate and i am very thankful to receive an email from ayende - developer behind NHibernate Query Analyzer.  In his email, he told me that NHibernate was able to recognize the fault in the mapping as he can see in the log and he will try to look at it if there is really something wrong.  i forgot to post in the NHibernate forums last week and was thankful that concerned developers like ayende was able to search through my blog these days.

i have never enabled logging for NHibernate and with his reply, i was eager to enable it to see what ayende meant.  First i encountered a probable bug that i was not able to output any logs (even if i configured lognet to output ALL levels).  I haven't introduced logging in my codes, since my current principle is i can still work around debugging and maybe i will insert logging before we ship the application.  I just introduced a static ILog variable in one of my business object being tested and luckily i was able to output NHibernate logs in the Output window. I wonder why that is so?

anyways, moving further, i also found out that NHibernate is also generating a GetSet Helper class for each mapped class and the one generating the exception was this class generator.  I just thought that the mapping files were successfully loaded and parsed the first time i encountered the exception, but after seeing the logs, it was encountered when the mapping files are being loaded and parsed. 

---

Posted 06-13-2006 3:52 PM by jokiz