Thanks for the info James. Removing the discriminator as an actual
property helped but now I've run into issue #95 (where the
discriminator and the version tag are in the wrong sequence.) I tried
three times to attach an example to the issue that replicates the
problem but each time Google barfed. Briefly, it's dependent on the
order of the DiscriminateSubClassesOnColumn() and Version() in the
ClassMap file. If the sequence is DiscriminateSubClassesOnColumn()
followed by Version(), Fluently.Configure() succeeds but a generated
hbm.xml file is invalid. If the sequence is Version() followed by
DiscriminateSubClassesOnColumn(), Fluently.Configure() failes but a
generated hbm.xml file is correct.
I'm sorry I don't know enough about the FNH source to offer a patch.
On Mar 6, 3:44 am, James Gregory <
jagregory....@gmail.com> wrote:
> You don't normally have the discriminator as an actual property in your
> entity too, it's usually just a column. That's not to say it's incorrect,
> just something I've not seen before. Perhaps try it without.
>