On Dec 15, 4:29 pm, James Gregory <[email protected]> wrote: > Fluent NHibernate != NHibernate. We're just a layer ontop of NH. Once we > pass off our mappings to NH, there's little we can do. We have plans to put > in a validation layer to try to catch the obvious cases (like missing Id) > before we pass off to NH, but the cryptic exceptions aren't our doing.
That sounds like a great idea. Automapping is a terrific technology, but, IMO, is being hamstrung by arcane error messages. There have been seveal times in the last few weeks I've been on the verge of chucking it. (Glad I didn't - thanks again to the people on this list who helped me out!) One of the biggest problems I see is that there's often no indication of which class or member that is causing the error. Would it be worthwhile if several of we Fluent NH users submitted requests to the NH team to put more specific info in their error messages (e.g. which class, which member, etc)? -Tom -- You received this message because you are subscribed to the Google Groups "Fluent NHibernate" 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/fluent-nhibernate?hl=en.
