ObjectDB ObjectDB

Internal Website Search

61-70 of 200 resultsRefresh

Version 2.5.6 enhancement problem solved by updating to version 2.5.7_03

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 ... and enhanced again if the classes were enhanced with an earlier version. But maybe build 2.5.7_03

OEM license, enhancer

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 ... That is correct. As long as you distribute your software with entity classes that have been enhanced

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

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

OEM enhancing

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 ... they should be enhanced to avoid the restriction of one million instances in the database (on end user machines). support Support

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

Remove of an entry from a @OneToMany collection is not possible if the enhancer is disabled

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 ... you for this report. It represents an issue with non enhanced classes, but it is not related to @OneToMany

Enhancer: non-zero exit code at exceptions

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. 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

Post-compile enhancement sometimes causes error in generic loops: incompatible types found: java.lang.Object: required: Entity

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 ... but it is inconvenient to have to remove generic loops just because of enhancement: for (Object os

Enhancer NullPointerException

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

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support