The highlighted changes regard events in Mapper.
With those events you can map a default that then will be overridden by patterns-appliers/customizers.
A usage example can be can be the set of Cascade to Cascade.Persist as default for many-to-one, one-to-one, many-to-many, one-to-many.
Even if the cascade was set to Persist, all appliers can override it if the property match a specific pattern.
The next release will be for NHibernate3.2.0 where I have ported some of ConfORM classes.
Inside NHibernate I have implemented some others classes/interfaces to give support to all NHibernate features.
I will you those classes/interfaces.
This may mean that ConfORM will give support to:
- idBag
- dynamic-components
- <join> (root of TablePerClass with properties splits)
- <subclass><join> (TablePerClassHierarchy with splits)
and.... here I would cry... even
- composed-id
- component as id
Perhaps I'll disable (inside ConfORM) the composed-id.
Bye.
--
Fabio Maulo