Hello, I use an IReturnBinder to put the result of a controller action, a view model, into the Propertybag. Now, some of these results implement ILayout, an interface, that has properties for the page's header, footer and navigation. My plan was/is to use a filter, that would execute AfterAction, open an ISession, pull the required data and transform it into the missing ILayout and place that info int the view model.
What seems to be the problem, is that at this point of time, using Rhino.NHibernate.Common.UnitOfWork (and Application), the Session is already closed (sometimes), the opened Transaction waits until it times out and keeps the thread running for that long. After a bunch of these requests, I have no threads left and the app dies. So, this is just a hunch, but it seems reasonable to me. Can anyone confirm this for me? Could I choose another approach, that would not suffer from this behavior? Asking @castle, could I place another, earlier hook, for the Filter to run? I think I could use a Factory to retrieve the view model with the ILayout already implemented, but this would require quite a few changes in a lot of places, so I am reluctant. -- Jan -- You received this message because you are subscribed to the Google Groups "Castle Project Users" 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/castle-project-users?hl=en.
