[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1907) make ComponentType operate more like EntityType
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1907?page=c...
]
Steve Ebersole commented on HHH-1907:
-------------------------------------
Well the important piece of "operate more like EntityType" is specifically
offloading of info to *something* maintained by the session factory. This something might
either be a new ComponentPersister, or perhaps the ComponentMetamodel directly (but even
if I go the ComponentPersister route, it would have a reference to the
ComponentMetamodel).
So short answer is yes
make ComponentType operate more like EntityType
-----------------------------------------------
Key: HHH-1907
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1907
Project: Hibernate3
Type: Improvement
Components: core
Reporter: Steve Ebersole
Assignee: Steve Ebersole
Specifically, we need to move all the code directly dealing with property-access,
instantiation, etc out of here. So where do we move it? Well, EntityType for example
moves this stuff off to the persisters; the type then just looks up the persister when
needed. Not sure we actually need a persister per-se for handling components; perhaps
just ComponentMetamodel is enough...
Why is this important? Well the way ComponentType is currently structured leads to the
need for certain configuration properties to be classloader scoped (static on Environment)
instead of SessionFactory scoped. This is painful for two in particular: 1) whether to
use reflection optimization and 2) bytecode provider.
Also, this change should allow us to cleanup how property accessors are built
--
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