ConfORM 1.0.1.5 was released (for NH3.1.0GA)

42 views
Skip to first unread message

Fabio Maulo

unread,
May 14, 2011, 12:53:40 PM5/14/11
to codec...@googlegroups.com
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

Fabio Maulo

unread,
May 16, 2011, 8:36:13 AM5/16/11
to codec...@googlegroups.com
Sorry for the 1.0.1.5 bins.
It was associated with a very early version of NH3.2.0... I'm going to recreate the package.
--
Fabio Maulo

Fabio Maulo

unread,
May 16, 2011, 8:42:57 AM5/16/11
to codec...@googlegroups.com
Fixed on the site and in NuGet
--
Fabio Maulo

Reply all
Reply to author
Forward
0 new messages