[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-5543) JEE bootstrapping should only parse and validate mapping files once
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5543?page=c...
]
Steve Ebersole commented on HHH-5543:
-------------------------------------
This is handled much differently on trunk. In 3.5 and prior eventually you always added a
{{Document}} to the {{Configuration}}, which of course lost the ability to report on
source file names. I improved that in 3.6 to use a custom {{XmlDocument}} instead that
wraps the {{Document}} with some other information called an {{Origin}}.
So I'll roll this change back on the 3.5 branch.
JEE bootstrapping should only parse and validate mapping files once
-------------------------------------------------------------------
Key: HHH-5543
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5543
Project: Hibernate Core
Issue Type: Improvement
Components: entity-manager
Affects Versions: 3.5.5, 3.6.0.Beta4
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Fix For: 3.5.6, 3.6.0.CR1
Time Spent: 1.8h
Remaining Estimate: 0h
Currently mapping files get parsed and validated twice during JEE bootstrapping:
# once in {{org.hibernate.ejb.Ejb3Configuration#addXMLEntities}} (from
{{org.hibernate.ejb.Ejb3Configuration#configure}}, from
{{org.hibernate.ejb.HibernatePersistence#createContainerEntityManagerFactory}})
# again to actually add it to the configuration from
{{org.hibernate.ejb.Ejb3Configuration#addClassesToSessionFactory}} (from
{{org.hibernate.ejb.Ejb3Configuration#configure}}, from
{{org.hibernate.ejb.HibernatePersistence#createContainerEntityManagerFactory}})
AFAICT, the first occurrence is used to identify classes for potential enhancement.
--
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