Home/ Questions/Q 4591928
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-21T22:27:55+00:00

I have a solution that was created with NHib 1.2 which we’re upgrading to

  • 0

I have a solution that was created with NHib 1.2 which we’re upgrading to NHib 3.0.

Our hbm file has the following property:

<property name="ContentId" column="ContentId" access="field.camelcase-underscore" />

The class doesn’t have a ContentId property. This was working fine in NHib 1.2 but now we’re getting getting the following exception:

Could not compile the mapping document: XXXX.Core.Domain.Video.hbm.xml ---> NHibernate.MappingException: Problem trying to set property type by reflection ---> NHibernate.MappingException: class Core.Domain.Video, Core, Version=1.0.0.29283, Culture=neutral, PublicKeyToken=null not found while looking for property: ContentId ---> NHibernate.PropertyNotFoundException: Could not find the property 'ContentId', associated to the field '_contentId', in class 'Core.Domain.Video'.

Why would this stop working? Is it still supported in NHib 3?

We have many many properties like this that we might need to add.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    NHibernate greatly improved its error messaging and diagnostics in NH2.X and again in NH3.X. You are telling NHibernate that you have a property and you want to map it via field access to a field named by _camelCase convention. You don’t have a property named ContentId and NHibernate is letting you know that you lied to it. 🙂

    Try updating your mapping to:

    <property name="_contentId" column="ContentId" access="field" />

    You will need to update any HQL or Criteria queries to use _contentId rather than ContentId. Another option would be to add a private ContentId property.

    • 0