 2 | with a classpath that includes access to all your classes. In that case the synthetic class generation mechanism will not be needed. The workaround with the changed classpath for Doctor and Explorer worked |
2 | objectdb.jar as downloaded as a classpath variable without success. Thanks OK. It runs now. Second ... in the .classpath file as shown below:
|
2 | 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 |
2 | 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 |
2 | 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 which that index is defined |
2 | 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 |
2 | unless exclude-unlisted-classes=true is specified in the persistence.xml file. The classpath root ... file (but not the entire classpath) are searched for annotated classes and XML data when you invoke |
2 | 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 |
2 | 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 |
2 | , 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 |