Comments on: Testing Immutable Entities with NHibernate http://jameskovacs.com/2007/11/04/testing-immutable-entities-with-nhibernate/ Wed, 21 Mar 2012 14:32:22 +0000 hourly 1 http://wordpress.org/?v=3.1 By: James http://jameskovacs.com/2007/11/04/testing-immutable-entities-with-nhibernate/comment-page-1/#comment-5262 James Tue, 14 Dec 2010 18:35:45 +0000 http://jameskovacs.com/2007/11/05/Testing+Immutable+Entities+With+NHibernate#comment-5262 @Ramon - Unfortunately if you declare your ctor as protected, you can't create instances of Invoice in unit tests without resorting to Activator.CreateInstance or a similar technique. My overall point of this post was that you might have readonly data that you want to insert into your database for testing purposes. This technique allows you to modify your NH configuration to allow inserts of readonly data during the setup of your integration tests, but not in your production code. @Ramon – Unfortunately if you declare your ctor as protected, you can’t create instances of Invoice in unit tests without resorting to Activator.CreateInstance or a similar technique. My overall point of this post was that you might have readonly data that you want to insert into your database for testing purposes. This technique allows you to modify your NH configuration to allow inserts of readonly data during the setup of your integration tests, but not in your production code.

]]> By: Ramon Smits http://jameskovacs.com/2007/11/04/testing-immutable-entities-with-nhibernate/comment-page-1/#comment-3985 Ramon Smits Thu, 18 Nov 2010 10:26:45 +0000 http://jameskovacs.com/2007/11/05/Testing+Immutable+Entities+With+NHibernate#comment-3985 If you want readonly data then just make the contructor PROTECTED. You classes should indicate what kind of behavior is allowed. NHibernate is only there to help you persist and retrieve your data in an efficient way. Using a protected contructor will allow nhibernate to create proxies but will not allow you to create an instance of that class. If you want readonly data then just make the contructor PROTECTED. You classes should indicate what kind of behavior is allowed. NHibernate is only there to help you persist and retrieve your data in an efficient way.

Using a protected contructor will allow nhibernate to create proxies but will not allow you to create an instance of that class.

]]> By: Bjorne Bjornson http://jameskovacs.com/2007/11/04/testing-immutable-entities-with-nhibernate/comment-page-1/#comment-138 Bjorne Bjornson Mon, 11 Jan 2010 15:32:30 +0000 http://jameskovacs.com/2007/11/05/Testing+Immutable+Entities+With+NHibernate#comment-138 Different Hibernate/NHibernate reference documentation versions do indeed state, that "you can set other properties (and even change the mapping metadata) by accessing the Configuration before you build the ISessionFactory". But the same docs do also state, that "immutable classes, mutable=false, cannot be updated or deleted by the application". For there is no "NHibernate will not permit INSERT (...) against the entity"[sic] at all, inserting just works as expected. I wonder what this article is all about then. Different Hibernate/NHibernate reference documentation versions do indeed state, that "you can set other properties (and even change the mapping metadata) by accessing the Configuration before you build the ISessionFactory". But the same docs do also state, that "immutable classes, mutable=false, cannot be updated or deleted by the application". For there is no "NHibernate will not permit INSERT (…) against the entity"[sic] at all, inserting just works as expected. I wonder what this article is all about then.

]]> By: Sean Chambers http://jameskovacs.com/2007/11/04/testing-immutable-entities-with-nhibernate/comment-page-1/#comment-137 Sean Chambers Sat, 28 Jun 2008 11:31:03 +0000 http://jameskovacs.com/2007/11/05/Testing+Immutable+Entities+With+NHibernate#comment-137 Great tip. I just ran into something like this during the week. I think how I solved it was to first insert the rows outside the scope of nhibernate and then ran tests against it. It worked but was a little smelly. This is a much better solution. Thanks! Great tip.

I just ran into something like this during the week. I think how I solved it was to first insert the rows outside the scope of nhibernate and then ran tests against it. It worked but was a little smelly. This is a much better solution. Thanks!

]]> By: Dario Quintana http://jameskovacs.com/2007/11/04/testing-immutable-entities-with-nhibernate/comment-page-1/#comment-136 Dario Quintana Mon, 05 Nov 2007 17:13:19 +0000 http://jameskovacs.com/2007/11/05/Testing+Immutable+Entities+With+NHibernate#comment-136 Hi James, nice trick and blog. @Ben: Yes, you could, everything you want before the buildSessionFactory(), the ISessionFactoy go to determinate the future sessions. Another thing that come to my mind it's that NHibernate at next version (or some next version) with the Entity-Name port will do dissapear the methods with typeof(...) definition, only the generics and entity-Name methods will stay. Best regards Hi James, nice trick and blog.

@Ben: Yes, you could, everything you want before the buildSessionFactory(), the ISessionFactoy go to determinate the future sessions.

Another thing that come to my mind it’s that NHibernate at next version (or some next version) with the Entity-Name port will do dissapear the methods with typeof(…) definition, only the generics and entity-Name methods will stay.

Best regards

]]> By: Ben Scheirman http://jameskovacs.com/2007/11/04/testing-immutable-entities-with-nhibernate/comment-page-1/#comment-135 Ben Scheirman Mon, 05 Nov 2007 15:11:55 +0000 http://jameskovacs.com/2007/11/05/Testing+Immutable+Entities+With+NHibernate#comment-135 Awesome! I didn't know you could do this. Awesome! I didn’t know you could do this.

]]>