I have issues mapping a class hierarchy:
namespace Tasks{
public class CapacityRequirement : DomainBase
{
public virtual Guid Id { get; set; }
...
public virtual Resslist Resource { get; set; }
}
public class PartRequirement: DomainBase
{
public virtual Guid Id { get; set; }
public virtual Matart Part { get; set; }
public virtual Mapark Machine { get; set; }
...
}
public class WorkPackage : DomainBase
{
public virtual Guid Id { get; set; }
public virtual IList<CapacityRequirement> CapacityRequirements {
get; set; } = new List<CapacityRequirement>();
public virtual IList<PartRequirement> Parts { get; set; } = new
List<PartRequirement>();
...
}
}
The Classes Resslist, Matart and Mapark are already mapped.
I'm trying to make two indexed lists in uni-directional one-to-many.
For some reason I'm getting An association from the table fst_
Part_Requirements refers to an unmapped class:
Mapark
but class is mapped.
What does work:
* Removing mapping for second collection (PartRequirements) from
WorkPackage-Mapping.
* Removing all many-to-ones from PartRequirement and CapacityRequirement.
(If I only remove all many-to-ones from PartRequirement, then the
CapacityRequirement class wont compile).
It looks for me as a bug...
Did someone had such an issue?
Should I start debugging NHibernate?
Best regards,
Konstantin
--
You received this message because you are subscribed to the Google Groups
"nhusers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/nhusers/02bf5d5b-a12b-487a-9dd6-140f0822f758%40googlegroups.com.
