For example, lately I've been fooling around with the mapping
configuration classes, to "manually" configure nhibernate (and fill
mappings from code, sort-of-fluentnh), and it took me quite a while to
figure out what was necessary.
For example (pseudo-names..):
method Mapping.AddPersistentClass(PersistentClass) adds a given
PersistentClass definition to the mappings.
Needs:
+ valid PersistentClass.Table.
+ EntityName
etc..
I know this mapping area might be considered internal to nhibernate,
but this same remark applies to other areas of NHibernate..
Just my 2 cents..
Regards,
Matthijs ter Woord
> --
> You received this message because you are subscribed to the Google Groups
> "nhusers" group.
> To post to this group, send email to nhu...@googlegroups.com.
> To unsubscribe from this group, send email to
> nhusers+u...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/nhusers?hl=en.
>
>
--
Fabio Maulo
include the new features of nh3 , Query, QueryOver, etc. |
--
You received this message because you are subscribed to the Google Groups "nhusers" group.
To post to this group, send email to nhu...@googlegroups.com.
To unsubscribe from this group, send email to nhusers+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.