Hi all,

I'm building a WCF service that emits a domain object that contains a Set<>, I noticed that when NHibernate loads an object containing a collection, it replaces the implementation of the iesi.collection with a NHibernate implementation (NHibernate.Collection.Generic.PersistentGenericSet).

The consumers of my service will not have the nhibernate.dll.
Is there any way to make NHibernate not switch out the implementation of the collection? I tried setting lazy to false but this had no impact.


thanks for your help.

NH is something intrusive with collections.
Any way you can implements you own IUserCollectionType.
An example is available on NH tests.
Bye.

Hi Fabio,

Can you please elaborate on your answer? We are facing the same issue. As we are new to NHibernate can you guide with specific links.

Thanks in advance,

Arvind.

Hi. The same question. WCF client will have the only assembly with domain entities.
Is it possible somehow to force NHibernate not to replace collections with it's own? Of course there will be not change tracking, so all items in collection will be updated during each save.