I'm pretty aware of what the Facility can do or not. I just want to know what you were doing. You know, from someone that marks a transaction as a readonly but still leave the commit/rollback working, we must expect everything.
Cheers, Henry Conceição On Tue, Oct 5, 2010 at 1:30 PM, Jordan Muscott <[email protected]> wrote: > > > On Oct 5, 4:50 pm, Henry Conceição <[email protected]> wrote: >> What we need is just a NHIbernate read only session. If the validation >> error occurs inside an transactional, an abort seems to be the natural >> path. >> Outside it, the read-only Session should cover the scenarios >> were a flush isn't desirable. >> >> How do you open and close the session during web requests? > > > The Castle NHibernate facility opens one NHibernate session per HTTP > request. Sorry to be rude, but I'm quite surprised that you have to > ask that. Can someone with experience of using Castle in a web > scenario please look at this as well? > > regards, > Jordan. > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Development List" 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-devel?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" 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-devel?hl=en.
