org.hibernate.tuple |
This package defines a runtime metamodel for entities at
the object level and abstracts the differences between
the various entity modes. It is unaware of mappings to
the database.
(This package is still undergoing maturation and will change
over the next few months.)
|
Java Source File Name | Type | Comment |
Dom4jInstantiator.java | Class | Performs "instantiation" based on DOM4J elements. |
DynamicMapInstantiator.java | Class | |
ElementWrapper.java | Class | Wraps dom4j elements, allowing them to exist in a
non-hierarchical structure. |
EntityModeToTuplizerMapping.java | Class | Centralizes handling of
EntityMode to
Tuplizer mappings. |
IdentifierProperty.java | Class | Represents a defined entity identifier property within the Hibernate
runtime-metamodel. |
Instantiator.java | Interface | Contract for implementors responsible for instantiating entity/component instances. |
PojoInstantiator.java | Class | Defines a POJO-based instantiator for use from the tuplizers. |
Property.java | Class | Defines the basic contract of a Property within the runtime metamodel. |
PropertyFactory.java | Class | Responsible for generation of runtime metamodel
Property representations. |
StandardProperty.java | Class | Represents a basic property within the Hibernate runtime-metamodel. |
Tuplizer.java | Interface | A tuplizer defines the contract for things which know how to manage
a particular representation of a piece of data, given that
representation's
org.hibernate.EntityMode (the entity-mode
essentially defining which representation).
If that given piece of data is thought of as a data structure, then a tuplizer
is the thing which knows how to
- create such a data structure appropriately
- extract values from and inject values into such a data structure
For example, a given piece of data might be represented as a POJO class.
Here, it's representation and entity-mode is POJO. |
VersionProperty.java | Class | Represents a version property within the Hibernate runtime-metamodel. |