 2 | one. However, you can open the old database in the Explorer (without entity classes in the classpath) and view ... when entity classes are not in the classpath? If I can reproduce this I should be able to get information ... about the new schema. I have tried to connect to the "old" db without entity classes in the classpath |
2 | schema (your entity classes and XML metadata if any) available in the the classpath (either in ... the classpath. Removing that temporary persistent field, and again opening the database when the up to date class is available in the classpath. This may fix the database. Please check and update. Hello |
2 | am using jpa 1.0 implement, but I do have objectdb.jar in my classpath. can anybody help? thanks Maybe you have an old JPA or ObjectDB JAR in your classpath before the new objectdb.jar file. What version of ObjectDB are you using? Thanks. I got it. I have javaee-api-5.jar in my classpath which causes the error hongsun |
2 | /PrimitiveValue.jdo"). I don't have such file on my classpath. So my question is: how can I prevent objectdb ... implementation in your web application or class path. Hi, On my classpath I have the entry ... of the classpath is dumped for each single exception. I even don't see a trace that is related to ObjectDB |
2 | .jar (my entity classes in it) in classpath but it doesn't work (new entities still dont show up in ... steps: Run the Explorer with the new class in the classpath:
java -cp <classpath> -jar explorer |
2 | a whole class? 2) What happens when we open the DB but not all entity classes exist in the classpath? ObjectDB ... itself was still available in the classpath. If we complete remove the class, it works as we hoped ... .UpdateDB.main(UpdateDB.java:28) If a class is not available in the classpath but needed by ObjectDB |
2 | : If you want an embedded database (H2, HSQL or Derby), please put it on the classpath ... within spring-boot-starter-data-jpa. No solution? :(( Spring Data JPA expects a JDBC driver in the classpath ... ), please put it on the classpath.
If you have database settings to be loaded from a particular |
1 | if you open the database in your application and the new class is available in the classpath ... specifying a classpath that contains the new class. > BTW, "describe table xxx" will show what index a column |
1 | are available on this page. Please verify that you only have objectdb.jar in the classpath and not ... in the classpath. Currently you can not set the objectdb.home or objectdb.conf system properties |
1 | 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 |