Castle Facilities NHibernateIntegration 与 Castle Facilities NHibernate
有人能解释一下这两者的区别吗？ 我想使用第二个设施提供支持的流畅的 Nhibernate。但我还想使用 http 模块（SessionWebModule）在视图支持中打开会话，这似乎位于第一个设施中。它们兼容吗，我应该同时使用吗？
Can anybody shed some light on the difference of these two?
I want to use fluent Nhibernate which the second facility provides support for. But I also want to use the http module (SessionWebModule) for open session in view support which seems to reside in the first facility. Are they compatible, should I use both?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我是 NHibernate Facility 的创建者和 Castle.Transactions 的提交者。 （不参与 NHibernate 集成设施）
我将 NHibernate 设施创建为仅 Windsor 设施类型的项目。它主要围绕每个事务的会话概念，而不是每个请求的会话概念。但是，您可以向 NHibernateFacility 的创建者传递一个枚举，该枚举使默认生活方式每个请求会话。
从版本号可以看出它们不兼容。 NHibernate 设施是全新的（但正在生产中，因为它非常非常小）。另一方面，NHibernate Integration 是官方产品。
NHibernate Facility 要求您使用目前处于测试版的 Transactions 3.0。 tx 支持完全存在，但不支持事务性 NTFS 位。
我在自己的项目中使用了自己的 NHibernate 工具，它运行得非常好。 YMMV。
I'm the creator of NHibernate Facility and the committer on Castle.Transactions. (not participating in NHibernate Integration facility)
I created the NHibernate facility as a Windsor-facility-only type of project. It works mostly around the concept session per transaction and not session per request. However, to the c'tor of the NHibernateFacility you can pass an enum that makes the default lifestyle session per request.
They are not compatible as you can see from the version numbers. The NHibernate Facility is brand new (but in production, because it's very very tiny). NHibernate Integration on the other hand is the official product.
NHibernate Facility requires you to use Transactions 3.0 which is beta at the moment. The tx support is fully there, but not the transactional NTFS bits.
I use my own NHibernate Facility for my own projects and it works really well. YMMV.