ObjectDB Database Search

ObjectDB versions in both the  pom.xml and the . classpath files. support Support I've tried

must also be available in the classpath , otherwise load would fail. If you run ObjectDB in an OSGi environment in

.objectdb.Enhancer" classpath = sourceSets["main"].runtimeClasspath args = listOf( "-cp", "build

change in your application to register the change, or run the Doctor with a classpath that contains your entity classes. support Support

with all the classes in your classpath . To add a new 'MyEntity' class - run a dummy query: " SELECT e

the following simple test (with your persistent classes in the classpath ): import javax.persistence

the server with a classpath that includes the new class files, although your workaround is also fine

your classes to the classpath of the Explorer and the Server, since methods are not stored in

for old ObjectDB jar files in the classpath . support Support Yes, you are right. We use also different

- please try to isolate the problem. The server should work well with no entity classes in the classpath . support Support

/persistence.xml file in the classpath 19:05:31.464 [main] DEBUG org.hibernate.jpa

because I can't seem to detect the classes on the classpath even at the moment when the LinkageError

.Enhancer'   classpath = sourceSets.main.runtimeClasspath   args '-cp', 'src/main/groovy

I've attached a test which fails with the error "ArrayIndexOutOfBoundsException: -1". It runs 10 threads which create and persist objects. The objects are based on application objects so its not a single class test I'm afraid but it is standalone. I'm running as follows: java - classpath objectdb

available in the classpath . support Support Thanks for your suggestion.. It solved my problem

(and possibly all your application jars) to the classpath of the server to make the method available on the server side. support Support

idea why java.sql.Date is not found in the classpath ? Which Java version are you using? Do you use

after the change has to be available on the classpath . Otherwise the upgrade will fail. Could you please confirm

in the classpath . support Support Just tried running the Doctor on a database with your model

. Could you please double check it (sometimes the old objectdb.jar file remains in the classpath and the wrong

Improved processing of some sorts of queries. Added support for using ObjectDB with JPA 1 jar in the classpath . Changed server start avoiding new process creation. Added logging for class loading and method finding problems. Fixed a bug in the results of IS [NOT] NULL queries. Fixed a bug in