Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

offload metadata information from ComponentType to SessionFactory

Description

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

Long term it would facilitate the ability to have hierarchies of components as well as loading components in a 2-phase-load paradigm like entities and collections.

Activity

Show:

Christian BeikovApril 4, 2024 at 11:44 AM

I'll close this as out of date, because this offloading happened in ORM 6 when we introduced EmbeddableRepresentationStrategy etc., which is now part of the runtime model.

Steve EbersoleOctober 22, 2008 at 5:11 AM

Added that requires which in the long term is correct to do this cleanly.

However, is far more ambitious than this issue and is therefore bound to the 4.x time-frame. Would really like to instead get this into earlier releases since it is very very useful.

Steve EbersoleNovember 9, 2006 at 2:47 PM

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

Josh MooreSeptember 27, 2006 at 5:12 PM

Steve, would this make it possible to get to more of the ComponentMetamodel?

Noticed this in ComponentType:

public ComponentType(ComponentMetamodel metamodel) {
// for now, just "re-flatten" the metamodel since this is temporary stuff anyway ()

What I find to be missing is access to the updatability/insertablity/etc. of the EmbeddedComponent properties.

Steve EbersoleJuly 14, 2006 at 1:43 AM

Also make the notion of EntityMode extensible, at least internally, while in here changing this code. The end-game being to eventually allow users to plugin in their own entity modes

Out of Date

Details

Assignee

Reporter

Components

Priority

Created July 14, 2006 at 1:42 AM
Updated April 4, 2024 at 11:44 AM
Resolved April 4, 2024 at 11:44 AM