[
http://opensource.atlassian.com/projects/hibernate/browse/ANN-303?page=co...
]
James Olsen commented on ANN-303:
---------------------------------
I take your point about the exporter. It was probably just an issue for me in what
I'm trying to achieve with my generation process. Although it seems to me from the
annotation point of view a given class can only have one Entity annotation which has only
one name. So this is at odds with your assertion. I guess you can have multiple hbm.xml
files for the same class where each one has a different entity-name but you couldn't
generate this from an annotated class. In fact from a annotation point of view the
cardinality is potentially the reverse, you could have multiple classes annotated with the
same Entity.name. Haven't checked if this is legal per the spec though.
I see no change in svn for the EntityBinder. Maybe someone has done some other sort of
fix but this looks like a clear bug where the PersistentClass entityName is being set to
the actual class name not the value of the Entity.name annotation.
Consider implementing @Entity(name=) through entityName
-------------------------------------------------------
Key: ANN-303
URL:
http://opensource.atlassian.com/projects/hibernate/browse/ANN-303
Project: Hibernate Annotations
Type: Improvement
Components: binder
Reporter: Emmanuel Bernard
Priority: Minor
Attachments: ANN-303-patch.txt
I'm doubtful but this might be a solution
http://jroller.com/page/MikeSlattery?entry=workaround_for_entity_name_alias
--
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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira