From: NHibernate J. <mik...@us...> - 2006-12-05 13:56:32
|
[ http://jira.nhibernate.org/browse/NH-824?page=all ] Sergey Koshcheyev updated NH-824: --------------------------------- Fix Version: LATER type: Improvement (was: Bug) NHibernate does not support generic entities at this time. GetClassname is not the only place where generics break existing assumptions. I'm leaving this report open to fix it later. > GetClassname cannot parse generic classnames > -------------------------------------------- > > Key: NH-824 > URL: http://jira.nhibernate.org/browse/NH-824 > Project: NHibernate > Type: Improvement > Components: Core > Versions: 1.2.0.Beta2 > Reporter: Michael Abraham > Fix For: LATER > Attachments: GetClassnameBug.zip > > There appears to be a bug in NHibernate.Util.StringHelper.GetClassname. The code assumes that the last period in a fully-qualified class name immediately precedes the unqualified class name. That is not true for generic classes. GetClassname gets the unqualified class name of the type parameter with ']' appended. I believe that the same issue may affect StringHelper.Unqualify when it is applied to class names, but I don't know when (or whether) that ever happens. The attached VS2005 solution illustrates the problem. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.nhibernate.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |