 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 | Improved processing of some sorts of queries. Added support for using ObjectDB with JPA 1 jar in the classpath. Changed server start avoiding new process creation. Added logging for class loading and method finding problems. Fixed a bug in the results of IS [NOT] NULL queries. Fixed a bug in |
1 | the explorer, because it says that the method doesn't exist. I tried adding the classpath in the explorer |
1 | Objectdb version 2.8.3: Java version is current: java -version openjdk version "11.0.9.1" 2020-11-04 OpenJDK Runtime Environment 18.9 (build 11.0.9.1+1) OpenJDK 64-Bit Server VM 18.9 (build 11.0.9.1+1, mixed mode) But activation complains: java -classpath objectdb.jar com.objectdb.Activator |
1 | 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 |
0 | line string editor by default. When the "Classpath for persistent classes and metadata" field ... are not available. Some features of the Explorer, however, do require setting the classpath ... only when the code of these methods is available using the specified classpath. The "Server |
0 | to the application's classpath. In this mode, the database file is locked for a single process, and multi user ... files to the classpath is the only requirement. Client-Server mode, however, is useful |
0 | execution on the server side, classes have to be added to the classpath of the server as |
0 | . If you add odbse.jar to the classpath, you can run the server simply by:
> java com.objectdb.Server |