6 | Query causes an nternal exeption)? support Support The reason was missing entity classes in the classpath during migration of the database |
6 | EntityManager.find(entityClass, primaryKey) is slow when accessing non-existent IDs the classpath 11:00:49.562 [main] DEBUG org.hibernate.jpa.HibernatePersistenceProvider - Located |
6 | Enhancement Check synthetic, i.e. apparently ObjectDB found real classes in the classpath for them (unless |
6 | objectdb:2.8.4 - Error occurred during initialization of boot layer.execution=ALL-UNNAMED --add-modules RTDEngine -Dfile.encoding=UTF-8 -classpath "C:\Program Files |
6 | ObjectDB and Hibernate in one JVM?, you may have to put ObjectDB and Hibernate in a specific order in the classpath (try both options |
6 | Storing methods? as an extension to JPA), the classes must be made available to the server JVM by adding them to classpath. support Support |
6 | enhanced object .. NOT enhanced annotation (or alternative XML, e.g package.jdo in the classpath). > Finnally we get an OutOfMemory |
6 | migration path from JPA / Hibernate might be straightforward. Just add objectdb.jar to the classpath and set ObjectDB as the provider in the persistence |
6 | ODB IndexActivation NullPointerException.1_01 in the classpath Testproject and forgot, that the 2.6.x was already included by a required |
1 | Compatibility Problems Upgrading from 2.6.9_04 to 2.7.6 is closed) and no old objectdb jar should remain in the classpaths. > and mismatched .odb$ write files |
