 1 | suspected that it was something related to the classpath as I had a similar problem when using openJPA as an interim solution. Its working perfectly now. wbotha |
1 | the following simple test (with your persistent classes in the classpath):
import javax.persistence |
1 | a resource at that path. You may try putting your jar file with your configuration resource before objectdb.jar in the classpath. tsichevski |
1 | the Explorer with all the classes in your classpath. To add a new 'MyEntity' class - run a dummy query |
1 | definition (either annotation in class or xml), or run the Doctor with this available in the classpath |
1 | (and possibly all your application jars) to the classpath of the server to make the method available on the server side. quasado |
1 | I've attached a test which fails with the error "ArrayIndexOutOfBoundsException: -1". It runs 10 threads which create and persist objects. The objects are based on application objects so its not a single class test I'm afraid but it is standalone. I'm running as follows: java -classpath objectdb |
1 | need to define the .odb in a specific location or include any additional jars in the classpath. I'll |
1 | ), the classes must be made available to the server JVM by adding them to classpath. lsitongia |
1 | you have JPA 1 jpa.jar in your classpath before objectdb.jar - this happens for example if you use old Glassfish version that contains JPA 1.0. dmoshal |