Well, I figured out that the NHibernate configuration wasn't properly
referencing the Common.DataObjects.dll for mapping files. So that
fixed the first error. Now it complains (rightfully so, RFTM) that I
can't use identity for the ID.

My question is then, what would you recommend as an alternative? If
all NewsItems are CalendarNewsItems in this scenario (any other
application would use a separate database), it effectively could use
identity, but I suppose it doesn't know that. Any forseeable problems
with using HiLo against a "fake" NewsItem table? I'd like the solution
to be compatible with other applications, which may or may not have
their own subclasses.

-- 
You received this message because you are subscribed to the Google Groups 
"nhusers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/nhusers?hl=en.

Reply via email to