You already posted this in the dev forums, but I'll answer it here because I'm sure others will be having the same issue. If you are using lazy loaded properties, you won't be able to unproxy the object. I haven't heard what the workaround is for this yet so things like nhibernate validator can work with these entity types.
On Sep 21, 1:14 am, pvginkel <[email protected]> wrote: > It seems that NHibernateProxyHelper.GetClassWithoutInitializingProxy > does return the correct class. I would still like to know what the > purpose of NHibernateUtil.GetClass is when it just returns the proxy > class for Castle. Anybody? > > On Sep 19, 9:31 pm, pvginkel <[email protected]> wrote: > > > > > > > > > With Spring, NHibernateUtil.GetClass returns the actual type of the > > entity the proxy is created for. For Castle however, I get the proxied > > type back. Is there a good reason for this and if so, how can I get > > the correct type? > > > I'm using the trunk of NH3. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
