ObjectDB ObjectDB

Internal Website Search

121-130 of 200 resultsRefresh
12

OEM: Too many persistable types (>10) - exceeds evaluation limit (error 1011)

that creates my application (with ObjectDB Enhanced classes) but my application fails with the error ... and activations in recent versions. Please make sure that your classes are OEM enhanced. See this forum thread. support Support Thank you for the link to the class enhancing confirmation checking code
12

Entity Update - Is the documentation up to date?

if your classes are not enhanced. If your classes are enhanced, these changes will not trigger making ... ) is changed, will that be detected? It's just changes to elements that are not detected in enhanced ... The behavior is different for enhanced classes and non enhanced classes. With non enhanced classes - any change
12

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
0

javax.jdo.spi.StateInterrogation

javax.jdo.spi Interface StateInterrogation This interface is implemented by a non-binary-compatible JDO implementation to provide state interrogation for non-enhanced persistent classes. A call to JDOHelper to get the status of an instance is handled internally if the parameter instance implements
0

javax.jdo.listener.ClearLifecycleListener

the enhancer, so access to fields is not mediated. Parameters: event - the clear event. Since: JDO 2.0
0

jdoPreDelete()

after this call are disallowed. This method is modified by the enhancer so that fields referenced can be used in the business logic of the method. Since: JDO 2.0
0

jdoPreClear()

Method javax.jdo.listener.ClearCallback void jdoPreClear() Called before the values in the instance are cleared. Transient fields should be cleared in this method. Associations between this instance and others in the runtime environment should be cleared. This method is not modified by the enhancer. Since: JDO 2.0
0

javax.jdo.listener.DeleteCallback

. Access to field values after this call are disallowed. This method is modified by the enhancer
0

preClear(event)

and others in the runtime environment should be cleared. This method is not modified by the enhancer
0

javax.jdo.spi.JDOImplHelper

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

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