You can create your own ICollectionMapperFactory and set that type to configuration property nhibernate.envers.collection_mapper_factory.
For “inspiration” you can look at this obsolute project, https://bitbucket.org/RogerKratz/nhibernate.envers.setfornet4, that made envers support NHibernate.SetForNet4 (before NH Core supported BCL’s ISet<T> out of the box). /Roger From: [email protected] [mailto:[email protected]] On Behalf Of codekaizen Sent: den 16 maj 2017 01:55 To: nhusers <[email protected]> Subject: [nhusers] Envers global ICustomCollectionMapperFactory implementation? We replace the NHibernate ByteCodeProvider to return custom implementations of NHibernate collection types (which support stateless sessions better). Since all collections are replaced, it would be helpful to globally replace the ICustomCollectionMapperFactory instance. Is there an option to set this configuration globally (e.g. allowing CollectionMetadataGenerator.addMapper to delegate completely to a user type), or must it be done on each property? -Rory -- You received this message because you are subscribed to the Google Groups "nhusers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To post to this group, send email to [email protected]<mailto:[email protected]>. Visit this group at https://groups.google.com/group/nhusers. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/nhusers. For more options, visit https://groups.google.com/d/optout.
