ObjectDB ObjectDB

Internal Website Search

131-140 of 200 resultsRefresh
13

ObjectDB Enincompatible with Quarkus?

that runs fine without enhancement but fails after classes are enhanced, see trace below. This line near ... : it seems that ObjectDB's enhancer adds __ to methods, which is incompatible with Quarkus's GraphQL ... of the "__" prefix, ObjectDB just uses its own corner with several enhanced methods that start with "__odb
12

Determining if Persistable Classes Have Trial Limitation

was that the Enhancer would not Enhance or sign the specified persistable classes without a valid key ... below which would seem to indicate success (classes not affected by trial limitations): [ObjectDB 2.7.6 Enhancer] 7 persistable types have been enhance How can I tell if a build does NOT occur with a valid key
12

Spring MVC Errors

configuration: org.codehaus.mojo:exec-maven-plugin:1.2:java (execution: enhance, phase: process ... > <id>enhance</id> <phase>process-classes</phase> <goals> <goal>java</goal> </goals> <configuration> <mainClass>com.objectdb.Enhancer</mainClass
2

javax.servlet.ServletException: Annotated methods must follow the JavaBeans naming convention. __odbHidden_getPropertyName

handles __odbHidden_getWidthPxSideBarLeft. webel Dr Darren Kelly The ObjectDB Enhancer modifies ... the Enhancer has to move the annotations to the proxy methods, but that would be more difficult ... and the old jar is not anywhere in the classpath. You are not using classes that have been enhanced by
2

Unexpected Exception during commit

to enhance I get: java.lang.NullPointerException at com.objectdb.o.CFG.t(CFG.java:272 ... ) at com.objectdb.o.JEN.<init>(JEN.java:59) at com.objectdb.Enhancer.enhance(Enhancer.java:66) at com.objectdb.Enhancer.enhance(Enhancer.java:87) at com.fastmodel.fastplan.db
0

javax.jdo.spi.JDOImplHelper

identity; newObjectIdInstance(Class, Object) should be used instead. If the class has been enhanced
0

javax.jdo.listener.LoadCallback

into this instance. This method is not modified by the enhancer. Derived fields should be initialized
0

newObjectIdInstance(pcClass)

(Class, Object) should be used instead. If the class has been enhanced for datastore identity, or
0

jdoPreStore()

Method javax.jdo.listener.StoreCallback void jdoPreStore() Called before the values are stored from this instance to the data store. Data store fields that might have been affected by modified non-persistent fields should be updated in this method. This method is modified by the enhancer
0

jdoPostLoad()

Method javax.jdo.listener.LoadCallback void jdoPostLoad() Called after the values are loaded from the data store into this instance. This method is not modified by the enhancer. Derived fields should be initialized in this method. The context in which this call is made does not allow access to other persistent JDO instances. Since: JDO 2.0

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