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
(→Mechanism in Java5/Java6) |
|||
| Line 1: | Line 1: | ||
<css>.source-xml {padding:4px;border:1px solid black;}</css><css>.source-java5 {padding:4px;border:1px solid black;}</css> | <css>.source-xml {padding:4px;border:1px solid black;}</css><css>.source-java5 {padding:4px;border:1px solid black;}</css> | ||
===== Dynamic Persistence ===== | ===== Dynamic Persistence ===== | ||
| − | Dynamic Persistence is defined as the ability to create a persistent entity class and use it within an application without <i>a-priori</i> the Java | + | Dynamic Persistence is defined as the ability to create a persistent entity class and use it within an application without <i>a-priori</i> the Java <tt>.class</tt> present on the classpath (or in some <tt>.jar/.war</tt> 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 persistent entities from their data stores based on types that are either defined in XML mapping files or are constructed within the running application. | ||
Revision as of 10:14, 17 September 2009
Dynamic Persistence
Dynamic Persistence is defined as the ability to create a persistent entity class and use it within an application without a-priori the Java .class 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 persistent entities from their data stores based on types that are either defined in XML mapping files or are constructed within the running application.