|
234
|
JPA / JDO Class Enhancer
ObjectDB Enhancer is a post compilation tool that improves performance by modifying the byte code of compiled classes after compilation. Enhancement is mainly for user-defined persistable classes ... . There is one case, however, where enhancement is required. Non persistable classes that access directly (not
|
|
60
|
[ODB1] Chapter 3 - Persistent Classes
the PersistenceCapable interface, and have the JDO Enhancer add the interface implementation automatically, as explained in section 3.3. ObjectDB's JDO Enhancer also adds a no-arg constructor ... only as fields in these classes. 3.3 JDO Enhancement The ObjectDB JDO Enhancer is a post compilation
|
|
56
|
Entity Management Settings
: |
|
44
|
Step 3: Add a Context Listener Class
GuestListener implements ServletContextListener { // Prepare the EntityManagerFactory & Enhance: public void contextInitialized(ServletContextEvent e) { com.objectdb.Enhancer.enhance ... ().getAttribute("emf"); emf.close(); } } The code above: Invokes the Enhancer to enhance
|
|
44
|
Step 3: Add a Context Listener Class
{ // Prepare the EntityManagerFactory & Enhance: public void contextInitialized(ServletContextEvent e) { com.objectdb.Enhancer.enhance("guest.*"); EntityManagerFactory emf ... (); } } The code above: Invokes the Enhancer to enhance the entity class, creates an EntityManagerFactory
|
|
39
|
[ODB1] Chapter 2 - A Quick Tour
, and a special tool, the JDO enhancer, adds the implementation automatically. The Person Persistent Class ... , it can easily become persistent using the JDO enhancer. JDO Metadata Every persistent class must be declared ... enhancement. 2.4 On The Fly JDO Enhancement On the fly JDO enhancement is the easiest way to use the JDO
|
|
26
|
Chapter 5 - Database Tools and Utilities
Describes the ObjectDB object database tools - the Explorer, the Server, the Enhancer, the Doctor and the Replayer.
|
|
22
|
Enhancer option to enhance all persitable types
Hello, can you add an option to the Class Enhancer to enhance all persistable types and ignore the NON persistable types. Like the Load Time Enhancement. btc_es BTC EmbeddedSystems A new argument (undocumented yet) was added to the Enhancer in build 2.6.2_06: > java -cp objectdb.jar com.objectdb
|
|
22
|
Post-compilation enhancement vs Automatic Run-time enhancement enhancement and automatic run-time enhancement. Testing exactly where and when the results are different ... depending on the enhancement stragegy). Can you please explain how this could possibly be so ? Why aren't the 2 enhancement techniques giving identical data access results ? webel Dr Darren Kelly
|
|
22
|
Cascading (persist) with a mix of enhanced and not enhanced entities
We find out that it is actual not possible to use enhanced and not enhanced entities together. Exist any limitations regarding the use of enhanced and non-enhanced entities? We work based feature and want to load other bundles as an artifact from the Nexus. These are always enhanced. To enhance
|
