[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1976) NamingStrategy.classToTableName receives only class name, not a fully qualified name as stated in javadoc
Dave Brondsema (JIRA)
noreply at atlassian.com
Fri Feb 23 09:12:34 EST 2007
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1976?page=comments#action_26245 ]
Dave Brondsema commented on HHH-1976:
-------------------------------------
This is a pretty big incompatible change (for those of us implementing classToTableName). What is the status of fixing this?
> 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