Anyone had luck making Castle work for their DotNetNuke module?

I first played with NHibernate and made it work without a problem.  But when it came to session management, the thing became hard to handle.  I then came accross Castle ActiveRecord which supposedly has a NHibernate facility that handles all of the session management.  I then proceeded to implement ActiveRecord on my module but was again stuck.

The problem is that I need to initialize ActiveRecord at the event application_start.  I cannot use HttpModule for that and I can't use Global.asax since I don't want to play with the core of DotNetNuke.

It seems I'm almost out of options and I really don't want to give up on ORM.

Any ideas would be greatly appreciated.

Thank you.

I would like to have only one session opened for every call I make to the database, instead of having to create a session before each call.  One way to do that is to create the unique session at the beginrequest event.  But then, if I want to connect to different databases, the thing just get out of hand.

That's why I'm looking at castle since it supposedly handle all that session management for you.  And that would be great :)

Do you know if EntitySpaces would help me with this?

How luck you're, man. here it is. http://www.codeproject.com/aspnet/NHibernateBestPractices.asp  It's the best article on asp.net I have ever read. Hope you agree with me after you read it.

Frank