Hi, There are also a few bugfixes and perf improvements on my github for the transactions project and the facility.
Currently on the develop branch of .Transactions, which is now the same source tree as AutoTx, is a fix for a null ref exception when registering the transaction manager manually in the kernel (not through facility that is), on dispose. The current master is the same externally (v2.5.1), develop branch contains these fixes. This changes how you register the transaction facility. This includes the read only transactions. I'm going to start following this branching method: http://nvie.com/posts/a-successful-git-branching-model/ I'll keep you posted on changes I make to them. The 2.5.1 version can be considered done though. Cheers Henrik On Apr 6, 2:35 pm, Maximilian Raditya <[email protected]> wrote: > On Wed, Apr 6, 2011 at 1:55 PM, TigerShark <[email protected]>wrote: > > > Sorry, yes, I do understand why the behavior is broken by NHibernate > > Facility and I've reported it as a bug > >http://216.121.112.228/browse/NH-262 > > Could you add in the bug report that it would also break with > IStatelessSession, in addition to ISession, since both methods in > LinqExtensionMethods.Query<T>() have the same buggy implementations? See > here: > > public static IQueryable<T> Query<T>(this ISession session) > { > return new NhQueryable<T>(session as ISessionImplementor); > } > > public static IQueryable<T> Query<T>(this IStatelessSession session) > { > return new NhQueryable<T>(session as ISessionImplementor); > } > > So both implementations need to be changed. > > -- > Regards, > > Maximilian Haru Raditya -- 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.
