Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/Features/Core"
< EclipseLink | Features
(→EclipseLink Core Functionality) |
|||
Line 1: | Line 1: | ||
− | { | + | {| width="100%" style="border: solid 2px #A3B1BF; background: #F5FAFF; padding: 15px;" | |
+ | |- | ||
+ | | | ||
+ | <h2 style="background-color:#cedff2; border-bottom:0px; border: 1px solid #a3b0bf; text-align:center; padding-top:4px;">PAGE UNDER CONSTRUCTION</h2> | ||
+ | |||
== EclipseLink Core Functionality == | == EclipseLink Core Functionality == | ||
Revision as of 15:50, 16 August 2007
ContentsPAGE UNDER CONSTRUCTIONEclipseLink Core FunctionalityThese core infrastructure features are leveraged by multiple persistence services. MappingEclipseLink offers developers the ability to map a persistent POJO domain model. These persistent object types known as entities allow developers to design and implement a domain model without coupling to a particular persistence service. EclipseLink allows the domin model to be implemented without:
Class DescriptorThe ClassDescriptor represents the mapping of a single class to one or more data source artifacts. The core functionality of the ClassDescriptor provides default support for constructing and accessing the attributes of an entity throgh the use of reflection.
Transactions
Sessions
Caching
UnitOfWork
|