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/Development/Dynamic/def1"
< EclipseLink | Development | Dynamic
(→Dynamic Persistence) |
|||
| (43 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
===== Dynamic Persistence ===== | ===== Dynamic Persistence ===== | ||
| − | Dynamic Persistence is defined as the ability to create a persistent entity | + | <onlyinclude> |
| + | Dynamic Persistence is defined as the ability to create a dynamic persistent entity and use it within an application without <i>a-priori</i> the entity's Java <tt>.class</tt> being present on the classpath (or in some <tt>.jar/.war</tt> archive). | ||
| − | Dynamic Persistence is | + | The purpose of Dynamic Persistence is to enable simplified data access where only mapping information is required and no concrete Java model is required. This allows applications with dynamic storage requirements to avoid coupling to static classes or require specialized handling of new types. The application uses standard EclipseLink APIs to read, create, modify, and remove dynamic persistent entities from their data stores based on types that are either defined in XML mapping files or are constructed within the running application. |
| − | + | </onlyinclude> | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
Latest revision as of 10:50, 17 September 2009
Dynamic Persistence
Dynamic Persistence is defined as the ability to create a dynamic persistent entity and use it within an application without a-priori the entity's Java .class being present on the classpath (or in some .jar/.war archive).
The purpose of Dynamic Persistence is to enable simplified data access where only mapping information is required and no concrete Java model is required. This allows applications with dynamic storage requirements to avoid coupling to static classes or require specialized handling of new types. The application uses standard EclipseLink APIs to read, create, modify, and remove dynamic persistent entities from their data stores based on types that are either defined in XML mapping files or are constructed within the running application.