 18 | other managed objects. Transparent update - changes are detected automatically. Code enhancement is optional ... . Can also be managed (started, restarted, stopped) from the command line. Class Enhancer Boosts performance by avoiding reflection and by using smart tracking. Non enhanced classes are also supported (by |
18 | update - changes are detected automatically. Code enhancement is optional (recommended before ... , restarted, stopped) from the command line. Class Enhancer Boosts performance by avoiding reflection and by using smart tracking. Non enhanced classes are also supported (by using reflection |
17 | ArrayIndexOutOfBoundsException with enhanced Entity |
15 | - you should only activate ObjectDB on developer machines. Classes that are enhanced by the ObjectDB Enhancer ... . Therefore, when ObjectDB runtime is bundled in a product that uses only signed enhanced persistable classes - activation by end users is unnecessary. |
15 | optimization engine. Detach / Attach. Support of persistent classes that are not enhanced. Improved ... trips in JDO bulk operations (e.g. refreshAll). JDO Enhancer supports enhancing of complete JAR files. |
15 | . Classes that are enhanced by the ObjectDB Enhancer (when using the OEM license) are signed ... only signed enhanced persistable classes - activation by end users is unnecessary. |
13 | enhancement (weaving) in Tomcat it has to be run with ObjectDB as a Java agent (javaagent:objectdb.jar). When using GlassFish - on the fly enhancement (weaving) is automatically enabled |
13 | >
enhance
process-classes
java
com.objectdb.Enhancer |
13 | ). Refresh your IDE cache. Rebuild your project using the new jar file and enhance your classes using the new Enhancer. Convert old database files using the ObjectDB converter: > java -jar converter.jar |
13 | > enhance
process-classes
java
com.objectdb.Enhancer |