NHibernate changing type

mweel · **Joined:** Fri Oct 27, 2006 3:41 am **Posts:** 8

I am using v.1.2.0.1001

What would cause a class to become:

CProxyTypeWorkListStateMachine_INHibernateProxy_ISerializable2

When I do a object.GetType()?

Here is the mapping file:

Code:

<?xml version="1.0" encoding="utf-8" ?>
<hibernate-mapping xmlns="urn:nhibernate-mapping-2.0">
   <class name="StateMachine.WorkList, StateMachine" table="WorkList">

      
      <id name="Id" type="Int64" unsaved-value="0">
         <column name="Id" sql-type="bigint" not-null="true" unique="true" index="PK_WorkList"/>
         <generator class="native" />
      </id>
      
      <discriminator column="Type" type="String"/>
      
      <property name="Name" type="String">
         <column name="Name" length="255" sql-type="varchar" not-null="true"/>
      </property>


      <property name="ValidatorType" type="String">
         <column name="ValidatorType" length="255" sql-type="varchar" not-null="false"/>
      </property>


      <property name="ValidatorAssemblyName" type="String">
         <column name="ValidatorAssemblyName" length="255" sql-type="varchar" not-null="false"/>
      </property>


      <property name="Error"/>
      <property name="OnlyAllowUpdate"/>
      

      
      <property name="Status" column="Status" type="StateMachine.Stat, StateMachine" /> 
      
      <many-to-one name="State" class="StateMachine.State, StateMachine">
         <column name="StateId" sql-type="bigint" not-null="true"/>
      </many-to-one>
      
      <bag name="Assignments" lazy="true" cascade="all-delete-orphan">
         <key column="WorkListId"/>
         <one-to-many class="StateMachine.Assignment, StateMachine"/>
      </bag>

      <many-to-one name="ExceptionWorkList" class="StateMachine.WorkList, StateMachine" cascade="all">
         <column name="ExceptionWorkListId" sql-type="bigint" not-null="false"/>
      </many-to-one>
      
      <map name="Parameters" table="WorkListParameters" lazy="true" cascade="all-delete-orphan"> 
         <key column="WorkListId"/> 
         <index column="`Key`" type="string"/> 
         <element column="`Value`" type="string"/> 
      </map>
         
      <subclass name="StateMachine.UserControl, StateMachine">
      </subclass>

      <subclass name="StateMachine.DotNetWorkFlow, StateMachine">

         <property name="WorkFlowType" type="String"/>
         <property name="WorkFlowAssemblyName" type="String"/>
         <property name="InstanceId" type="String"/>
         
         
      </subclass>
            

   </class>
</hibernate-mapping>

Thanks,

Marty

gert · **Joined:** Thu Jan 19, 2006 4:29 pm **Posts:** 348

Lazy loading.

Gert

guymahieu · **Joined:** Sat Sep 09, 2006 5:55 am **Posts:** 23

If you want to know the type name of your persistent class, you can always use NHibernateUtil.GetClass(object) in stead of object.GetType().

mweel · **Joined:** Fri Oct 27, 2006 3:41 am **Posts:** 8

Also none of my simple casts are not working. It seems like there is something else funny going on here.

dotNetWorkflow = (StateMachine.DotNetWorkFlow)this.WorkItem;

Unable to cast object of type 'CProxyTypeWorkListStateMachine_INHibernateProxy_ISerializable2' to type 'StateMachine.DotNetWorkFlow'.

Also, none of my other classes have this behavior.

Please help, thanks in advance.

Marty

mweel · **Joined:** Fri Oct 27, 2006 3:41 am **Posts:** 8

Guys,

I down graded to the old version and all is working well again.

I think the issue is, when using the new version you need to you interfaces for everything. Especially if you are using a lot of subclasses, etc. It appears the new version of dynamicproxy?? changed the way it handles the proxing of classes (this might explain why everything needs to be virtual now??)

This way your objects can be compared to interfaces vs. classes.

These are more questions than facts.

I will have to stay w/ version because I have way to many classes to turn into interfaces.

--

I think people should be warned about this because of the impact.

For me this impact was:

1) Cannot cast objects to their actual type, because of the proxy objects being inserted.

2) Could not use the normal GetType() of the object. This is important because global functions that I use may or may not be working on nhibernate objects.

c) Anywhere else you are using the typing information.

Marty

grennis · **Joined:** Sat Mar 25, 2006 9:16 am **Posts:** 150

Naturally you cant cast them, as they are different objects.

Just set lazy="false" if your class tag in your .hbm file.

abombss · **Posted:** Sat Oct 28, 2006 2:26 pm

My understanding of the changes with proxies was nhibernate actually checks on configuration if members of classes are virtual to ensure dynamic proxy can correctly proxy the class. In previous versions, this check never happened and caused errors with dynamic proxy if you tried to execute a non-virtual member of a proxy.

Of coarse to properly create a proxy it needs to proxy a class that can be subclassed ie. non sealed with virtual members, or an interface.

One of the reasons I can't stand Microsoft API's. They never program to interfaces and almost always make some members of there classes for extension non-virtual.

mweel · **Joined:** Fri Oct 27, 2006 3:41 am **Posts:** 8

I think it should be noted that interfaces should always be used then when creating nhibernate classes then.

Otherwise the new version will cause you a lot of greef.

Marty