NHibernate Duplicate class/entity mapping problem?

You are adding the file or assembly containing the mapping twice to your Configuration object.

This sounds like it might be right. Currently I'm loading the Configuration object in the assembly, and making another one inside my unit test class so I can export the schema. Is there a different way to handle this?

– Patrick McDaniel Sep 13 '10 at 15:21 You should build your configuration in a single place, but the problem is in the way you add the mappings. You should post the code for that. – Diego Mijelshon Sep 13 '10 at 15:48 While this answer didn't fully get me to an end result, it did set me along the path.

Had I posted the rest of my HBMs I'm sure it would have been figured out. In the Youth hbm I reference the Parent, and other classes. So when you add your Assemblies to the Configuration object you only need to add the Youth object.At least that is what fixed my problem.

– Patrick McDaniel Sep 17 '10 at 23:40.

Make sure you are not doing both of these: //Code Configuration var cfg = new Configuration(); cfg.Configure(); cfg. AddAssembly(typeof(Employee). Assembly); // Presuming Employee resides in "MyAssembly" as seen below.

And then //. Config configuration.

I had this problem, and solved it by putting this statement in hibernate.cfg. Xml file: org.hibernate.cache.NoCacheProvider.

As it gives a duplicate class entity mapping I can only imagen that you have two or more *.xml. Hbm files referring to the same . Net class.

Make sure that the xml class element for your Youth class does not have the same value for the name attribute.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.

Related Questions