[hibernate-issues] [Hibernate-JIRA] Resolved: (ANN-561) EntityBinder should provide the Fully Qualified Name of entities to the NamingStrategy.

[Emmanuel Bernard (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/ANN-561?page=all ]
     
Emmanuel Bernard resolved ANN-561:
----------------------------------

    Resolution: Duplicate

> EntityBinder should provide the Fully Qualified Name of entities to the NamingStrategy.
> ---------------------------------------------------------------------------------------
>
>          Key: ANN-561
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-561
>      Project: Hibernate Annotations
>         Type: Improvement

>   Components: binder
>     Versions: 3.2.1, 3.2.0.ga
>  Environment: JBoss 4.0.5.GA with last jboss-EJB-3.0_RC9_Patch_1 (Hibernate Annotations 3.2.0.GA).
> Oracle 10g. (Actually the issue is independent of the database backend)
>     Reporter: Saverio Trioni

>
>
> When implementing a custom NamingStrategy for table binding, the only information that is accessible by the strategy are the names of the classes, possibly up to the outer class, but all package information is lost.
> In a big project with multiple packages, it is often good to mark the tables with some information of the package.
> For instance, a class com.example.music.Country (specialization of Genre) should be able to be mapped to the table MUSIC_COUNTRY and com.example.geography.Country to the table GEOG_COUNTRY. Even sorting out omonimies, there is a matter of clarity (at the expense of name length) for the name of the tables.
> The point is to do this without touching the @Table(name="") annotation, using just default behaviour.

-- 
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