Internal Website Search

101-109 of 109 results

Enhancement Check

synthetic, i.e. apparently ObjectDB found real classes in the classpath for them (unless

javax.jdo.JDOUserException Failed to locate field field exampleField using reflection (error 363)

to the classpath . That way the issue is not happening. thamal Tomas Hamal

objectdb:2.8.4 - Error occurred during initialization of boot layer

.common.execution=ALL-UNNAMED --add-modules RTDEngine -Dfile.encoding=UTF-8 - classpath "C:\Program Files

ObjectDB and Hibernate in one JVM?

, you may have to put ObjectDB and Hibernate in a specific order in the classpath (try both options

Storing methods?

ObjectDB as an extension to JPA), the classes must be made available to the server JVM by adding them to classpath . support Support

enhanced object .. NOT enhanced

/ @PersistenceCapable annotation (or alternative XML, e.g package.jdo in the classpath ).  Finnally

JPA example is failing

.encoding=UTF-8 - classpath /home/svcid/projects/points-console/target/classes:/home/svcid/.m2

migration path from JPA / Hibernate

code - switching to ObjectDB might be straightforward. Just add objectdb.jar to the classpath

Compatibility Problems Upgrading from 2.6.9_04 to 2.7.6

is down and the database is closed) and no old objectdb jar should remain in the classpaths