 1 | might be the result of another issue - please try to isolate the problem. The server should work well with no entity classes in the classpath. webel |
1 | the classpath. This method is used in this tutorial. The error message that you got when trying to invoke |
1 | need to define the .odb in a specific location or include any additional jars in the classpath. I'll |
1 | on the com.objectdb.objectdb plugin. Adding objectdb.jar to the plugin runtime classpath. Fixing "SELECT p |
1 | is to run the server with a classpath that includes the new class files, although your workaround |
1 | the database after the schema change in your application to register the change, or run the Doctor with a classpath that contains your entity classes. Bimal |
1 | >
Otherwise, ObjectDB may search and register all the entity classes in the classpath. Crispy |
1 | . Could you please verify that there is no old objectdb.jar in the classpath and you are actually using a recent ObjectDB version? sjzlondon |
1 | ) and no old objectdb jar should remain in the classpaths. > and mismatched .odb$ write files. When a database |
0 | the enhancer from the command line. First, the classpath has to be set to include ObjectDB and JDO jar files. For example: On Windows command:
> set classpath=%classpath%;.;c:\objectdb\lib\odbfe.jar;c:\objectdb\lib\jdo.jar
On Unix sh / bash shell:
% CLASSPATH=${CLASSPATH}:.:/objectdb/lib |