I see that now in the documentation about duplicate class names and the auto-import attribute - thank you!
But the line above it in the documentation also states that if you are using assembly and namespace attributes then you don't have to use fully quallified class names. I am using both assembly and namespace attributes. Is the duplicate class naming an exception to this statement - that I still have to use auto-import=false even though I am using assembly and namespace attributes? Or is this a real bug after all? Thanks for your help in clarifying this!!! -Erk On Jan 7, 4:00 pm, "Fabio Maulo" <[email protected]> wrote: > auto-import="false" > > 2009/1/7 emarley <[email protected]> > > > > > When I create 2 mappings to the same table that are in different > > namespaces but have the same name, I get an error from nHibernate that > > they are duplicates. > > > Shouldn't I be able to create the same named class but in different > > namespaces? It seems that nHibernate is internally putting all the > > classes into a "global" namespace. > > > -Erk > > -- > Fabio Maulo --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
