[hibernate-issues] [Hibernate-JIRA] Updated: (HHH-1976) NamingStrategy.classToTableName receives only class name, not a fully qualified name as stated in javadoc

Samppa Saarela (JIRA) noreply at atlassian.com
Wed Feb 7 07:05:41 EST 2007


     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1976?page=all ]

Samppa Saarela updated HHH-1976:
--------------------------------

    Attachment: hibernate-annotations-3.2.1.patch.txt

This bug was due to misusage of default entity name which is unqualified class name according to EJB3 spec to derive the table name using given NamingStrategy. This patch fixes the issue.

> NamingStrategy.classToTableName receives only class name, not a fully qualified name as stated in javadoc
> ---------------------------------------------------------------------------------------------------------
>
>          Key: HHH-1976
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1976
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.1.3, 3.2.0.cr2
>     Reporter: Lóránt Pintér
>  Attachments: hibernate-annotations-3.2.1.patch.txt
>
>
> I have a custom NamingStrategy that overrides classToTableName in EJB3NamingStrategy. Prior to upgrading to Hibernate 3.1.3, my NamingStrategy implementation received the correct classnames as documented in the javadoc at http://www.hibernate.org/hib_docs/v3/api/org/hibernate/cfg/NamingStrategy.html#classToTableName(java.lang.String)
> Since then, it only receives the name of the class without the package specification. I tried upgrading to 3.2.0.cr2, but it didn't help.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira





More information about the hibernate-issues mailing list