[Hibernate-issues] [Hibernate-JIRA] Resolved: (ANN-377) EntityBinder should use full qualified class names instead of class names

[Emmanuel B. (JIRA) <no...@at...>]

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

    Resolution: Rejected

yes but this behavior is as per the spec.
A workaround is to use xml overriding on integration or force your team to use @Entity(name="f.q.c.Name")

> EntityBinder should use full qualified class names instead of class names
> -------------------------------------------------------------------------
>
>          Key: ANN-377
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-377
>      Project: Hibernate Annotations
>         Type: Improvement

>   Components: binder
>     Versions: 3.2.0.cr1
>  Environment: all
>     Reporter: Thomas Weber

>
>
> EntityBinder should use the full qualified class name to bind entities to simplify the use of entities with the same class name in larger projects. If the components of the project are from different developers the work-around with @Entity(name="someName") is not really useful, since it may not be possible to adapt the affected classes (i.e. if you do not have access to the source code)
> The performance impact should be rather small since the String.equals(Object) method compares hashcodes first, so the String.length() is a minor factor for the speed of comparisons.

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