 1 | that you get may indicate that objectdb.jar is not found in the classpath (i.e. JPA is available but not ... .java:722) It looks like a classpath issue. Maybe objectdb.jar is available only in compilation |
1 | you need to: Have the JAR file in the classpath that is available to ObjectDB. Sometimes setting ... you have to make sure that the path is included in the application classpath before the jar file |
1 | the classpath during enhancement? When a class is missing, ObjectDB Enhancer tries to overcome this by ... the classpath at that moment and I am curious why the ObjectDB Enhancer even cares about my non-jpa |
1 | X not found". I found an option to put a classpath for persistence objects and metadata, where I ... is automatically deleted. To see serialzable objects in the Explorer try to add the classpath to the JVM |
1 | the @index annotation in your entity class. Open the database with the up to date class in the classpath ... 2 may be skipped if you run the Doctor (step 3) with your up to date classes in the classpath. omi |
1 | , Bndtools 3.3.0). In order to build the code, you need to have lombok in the classpath (https ... is produced by JPA if it cannot find an appropriate JPA implementation in the classpath |
1 | the Explorer with your classes in the classpath. It may make a difference and serve as a workaround. Thanks ... the Explorer with no classes in the classpath, the Explorer uses the schema as defined in the odb file |
1 | us a lot of problems with our CI.
classpath="${project.root.dir}lib/*;${project.root.dir ... ) when there are multiple logging frameworks present on classpath. Nice description of this issue |
1 | the classpath more than once and loaded more than once (by different class loaders). Please verify ... a libs directory on the root of the eclipse project and then add it to the classpath runtime for each |
1 | available in the classpath. Build 2.5.1_02 should fix most cases. Adding the classes to the Explorer classpath may still be needed in some cases. AlphaOne |
