 258 | 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 |
58 | {
// 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 and creates an EntityManagerFactory |
58 | 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 |
38 | Describes the ObjectDB object database tools - the Explorer, the Server, the Enhancer, the Doctor and the Replayer. |
34 | :
<enhancement agent="true" reflection="warning" />
The <enhancement> element specifies enhancement related settings: The agent attribute (whose value is "true" or "false |
28 | 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. A new argument (undocumented yet) was added to the Enhancer in build 2.6.2_06:
> java -cp objectdb.jar com.objectdb.Enhancer -noaware |
28 | 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 |
28 | 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 ? There shouldn't |
27 | Hi I think I have found a bug : - I have enhanced a class but when I tried to persitst it I got ... we get an OutOfMemory expeption. b > I have enhanced a class but when I tried to persitst it I got an error ... the result of no enhancement but of a missing @Entity / @PersistenceCapable annotation (or |
26 | objectdb-2.6.9_02 (with "objectdb.temp.no-enhancement-crc-check" system property) The following ... value of field property Element.id using reflection - Possible cause for "Enhancement of type ... -compile, pre-deployment Ant script invoked using Clean and Build that enhances every entity class in |