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) |
(→Dynamic Persistence) |
||
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 class existing (no <tt>. | + | 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 class existing (no <tt>.class</tt> file on the classpath or in the relevant <tt>.jar/.war</tt> archive). |
− | + | ===== Mechanism in Java5/Java6 ===== | |
− | + | In order to create a Java class at runtime without the use of the <tt>javac</tt> compiler, the use of a custom ClassLoaderer is required, | |
− | + | along with a bytecode manipulation library (such as [http://asm.objectweb.org ASM] or some other [http://www.java-source.net/open-source/bytecode-libraries framework]). | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + |
Revision as of 14:47, 31 August 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 existing (no .class file on the classpath or in the relevant .jar/.war archive).
Mechanism in Java5/Java6
In order to create a Java class at runtime without the use of the javac compiler, the use of a custom ClassLoaderer is required, along with a bytecode manipulation library (such as ASM or some other framework).