Ah, thank you, the attribute initialization wasn't working so I had to use an explicit call in a static constructor.
The symptoms are consistent with NHibernate forgetting the mapping for the object: when there is no mapping for a class, NHibernate returns empty lists. Behavior I have observed is permanent failure of retrievals, success of retrievals, and success followed by failure. I have not observed failure followed by success. The program logs stuffing mapping files into NHibernate; the mapping files are indeed being stuffed. There are about 170 mapped classes with 5-10 properties each; is there a limit on how many classes or properties can be mapped? Again, thanks, and any ideas are appreciated. -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/nhusers. For more options, visit https://groups.google.com/d/optout.
