ObjectDB ObjectDB

Internal Website Search

41-50 of 115 resultsRefresh

Embedding ObjectDB on server application

The error message that you get may indicate that objectdb.jar is not found in the classpath (i.e ... .java:615) java.lang.Thread.run(Thread.java:722) Flying Banana Jiacong Xu It looks like a classpath

Unexpected internal exception during set field of an Embeddable to null

feature separately, as long as the classpath that is available to the Enhancer includes ... versions from the classpath. support Support We have further embedded classes derived from

Eclipse plugin problem (using ObjectDB as a separate bundle)

" menu and try the action again. I tried to use objectdb.jar as downloaded as a classpath variable ... Support In the plugin you sent me, there is an entry in the .classpath file as shown

javax.persistence.PersistenceException: No Persistence provider for EntityManager named in Karaf 4.0.7 and OSGi DS test

, Bndtools 3.3.0). In order to build the code, you need to have lombok in the classpath (https ... implementation in the classpath. You must make sure that ObjectDB is available in the context class

alter table

and the new class is available in the classpath, but this is indeed a step that has to be done. Alternatively, I think that you may run the Doctor specifying a classpath that contains the new class

WebSphere Liberty Configuration

? On the server classpath? Do you have other JPA implementations in the classpath

Unable to persist TreeMap

available in the classpath. support Support Build 2.5.1_02 should fix most cases. Adding the classes to the Explorer classpath may still be needed in some cases. support Support

DB Explorer and Doctor unable to open DB file

and the Explorer with a classpath that includes access to all your classes. In that case the synthetic ... classpath for Doctor and Explorer worked. I made a starting script for them, so I am willing to use

Configuration and Activation Code in ObjectDB 2.x

that you only have objectdb.jar in the classpath and not odbee.jar, which is an old ObjectDB 1.x jar ... if your JAR is preceding the objectdb.jar in the classpath. Currently you can not set the objectdb

Errors after unexpected server shutdown

the index, i.e. access the database with a class (in the classpath) in which that index is not defined, and then again redefine the index by accessing the database with a class (in the classpath) in

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