9 | Modifying something with Explorer -> app JPQL with Enum doesn't work anymore the Explorer with your classes in the classpath. It may make a difference and serve as a workaround ... with the Explorer (just that when you use the Explorer with no classes in the classpath, the Explorer uses |
9 | Unable to persist TreeMap available in the classpath. support Support Build 2.5.1_02 should fix most cases. Adding the classes to the Explorer classpath may still be needed in some cases. support Support |
9 | Embedding ObjectDB on server application The error message that you get may indicate that objectdb.jar is not found in the classpath (i.e ... .java:615) java.lang.Thread.run(Thread.java:722) Flying Banana Jiacong Xu It looks like a classpath |
9 | Problem Using Reflection to ObjectDB in the ordinary application classpath or the thread context classpath, so no synthetic |
9 | alter table and the new class is available in the classpath, but this is indeed a step that has to be done. Alternatively, I think that you may run the Doctor specifying a classpath that contains the new class |
9 | Is there an administration tool with which I could create extra indexes? the classpath in order to update the schema. Run the ObjectDB Doctor (in repair mode) to build the new index. Step 2 may be skipped if you run the Doctor (step 3) with your up to date classes in the classpath. support Support |
9 | Configuration and Activation Code in ObjectDB 2.x that you only have objectdb.jar in the classpath and not odbee.jar, which is an old ObjectDB 1.x jar ... if your JAR is preceding the objectdb.jar in the classpath. Currently you can not set the objectdb |
9 | OEM Enhancer causing Jenkins job to freeze us a lot of problems with our CI. <java classpath="${project.root.dir}lib/*;${project.root.dir ... frameworks present on classpath. Nice description of this issue can be found here: http://stackoverflow.com |
1 | Feature suggestion: auto-detection of entities via persistence.xml extension. The classpath root that contains the persistence.xml file and any jar file specified with jar-file in the persistence.xml file (but not the entire classpath) are searched for annotated classes and XML |
1 | Errors after unexpected server shutdown the index, i.e. access 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 |
