About Enhancer

Hello, 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. Thank you for this report. Starting build 2.6.1_04 the Enhancer exits with non zero code on errors. Note that System.exit is now invoked

for each customer system when we are using enhancer. As we want to ship a standard database with the system which was created before having the OEM license and before adding enhancer to our maven ... you distribute your software with entity classes that have been enhanced by the Enhancer in OEM mode

Hello! 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 ... . It represents an issue with non enhanced classes, but it is not related to @OneToMany collection. Any change

After 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 ... build 2.5.6 should also support Java 8, but the project has to be rebuilt and enhanced

I'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

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 ... error is not related to the Enhancer fix, but to another fix (issue #1373). Please try build 2.5.5_02. mosi0815

is thrown during an attempt to load a class in order to check if it needs enhancement. As you noted, this class is not related to ObjectDB and does not need enhancement, but the exception is thrown ... the logging level of this ObjectDB component to ERROR:

Hello, I have question regarding OEM licence enhancement.
@OneToMany(fetch = FetchType.EAGER ... >(); Are these classes(SomeClass, SomeClass2), when not enhanced, limited by number 1 million instances in DB? Thanks Marta If SomeClass and SomeClass2 are entity classes they should be enhanced to avoid

I have moved from automatic run-time enhancement to explicit post-compile enhancement in an Ant build.xml in a NetBeans web app, and sometimes on editing a file that performs a generic for loop ... to have to remove generic loops just because of enhancement:
for (Object os : steelMaterials.getL_Steel

de.tud.stg.emergent.policy.persistence.PolicyEntity.policyString using enhanced method
at org ... de.tud.stg.emergent.policy.persistence.PolicyEntity.policyString using enhanced method
at org.apache ... enhanced method" . ClassCast error was only once by me... --- I tried to use External Objectdb Server