83 | Option or strategy to disable/skip runtime enhancement checks (to improve load time)?On startup of a Maven-based web app there is verbose logging of object checking whether enhancement ... . For example, it is checking whether PrimeFaces JSF toolkit classes are enhanced. I am using Maven-based compile-time enhancement applied to entity modules (only), so I know these checks |
83 | Enhancement from gradle build fileJust wondering if it's possible to add enhancement in the gradle build file after compilation ... Moshal The following seems to work: task enhance(type: JavaExec) { main = 'com.objectdb.Enhancer ... .model_dir_two.*' } compileGroovy.finalizedBy(enhance) note, for java, you want compileJava instead of compileGroovy. dmoshal David Moshal |
83 | Version 2.5.6 enhancement problem solved by updating to version 2.5.7_03After updating some of my code to java 8, enhancement threw "unexpected" exceptions from ... have been related to the java 8 update. In any event, my enhancement problem went away when I updated ... and enhanced again if the classes were enhanced with an earlier version. But maybe build 2.5.7_03 |
82 | Java 8 Enhancer Problem transformers on the classpath. This is normaly not a problem because the ObjectDB enhancer ignores non @Entity or already enhanced classes but in conjunction with new Java 8 class files it throws ... after the update to 2.5.5_01. mosi0815 Ralph Moser The new error is not related to the Enhancer fix |
82 | WebService : Failed to get reference value of field using enhanced method de.tud.stg.emergent.policy.persistence.PolicyEntity.policyString using enhanced method at org ... enhanced method at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531 ... get always this error : "Failed to get reference value of field using enhanced method" . ClassCast error |
82 | Not Enhanced: ...: com.objectdb.o.TEX: Type ..._$$_javassist_1 is not found enhancement. As you noted, this class is not related to ObjectDB and does not need enhancement ... this exception, or decrease the logging level of this ObjectDB component to ERROR: <logger name="enhancer |
16 | Remove of an entry from a @OneToMany collection is not possible if the enhancer is disabledHello! When the JPA entities are not enhanced the removal of an entry from a @OneToMany collection ... .getChildEntityContainer().remove("01"); does not work correctly with not enhanced JPA entities ... you for this report. It represents an issue with non enhanced classes, but it is not related to @OneToMany |
16 | Enhancer: non-zero exit code at exceptionsHello, we have found that the enhancer returned an non-zero exit code on errors. You can change this so that the error of the enhancers can be detected. btc_es BTC EmbeddedSystems Thank you for this report. Starting build 2.6.1_04 the Enhancer exits with non zero code on errors. Note |
16 | Feature suggestion: Improved Maven Enhancer supportThere may a way to achieve recursive application of the enhancer using the maven plugin approach ... >com.objectdb.Enhancer</mainClass> <!-- List of your packages --> <arguments ... can be scanned automatically and enhanced if necessary. support Support |
16 | Enhancer NullPointerExceptionI'm getting the following stack trace when running the enhancer on one of my jars: [ObjectDB 2.3.2_04] null java.lang.NullPointerException at com.objectdb.o.JEL.L(JEL.java:633 ... .objectdb.Enhancer.main(Enhancer.java:32) Please let me know if you need any further information |
