6 | javax.persistence.PersistenceException. Adding objectdb.jar to the plugin runtime classpath. Fixing "SELECT p FROM Point p" to "SELECT p FROM |
6 | OEM: Too many persistable types (>10) - exceeds evaluation limit (error 1011) to get such messages unless ObjectDB cannot find your entity classes in the classpath. When an entity |
6 | Mismatch client-server protocol prefix version 2.6.2. Client version 2.6.2. Also there's only one objectdb jar on the classpath |
6 | Connection performace after upgrade to objectdb 2 on looking for classes and JDO metadata in the classpath (for synchronization with the database |
6 | Type xxx is not found (error 301) on my EntityManager Probably you have JPA 1 jpa.jar in your classpath before objectdb.jar - this happens |
6 | EntityManager getMetamodel() causes crash-unit> </persistence> Otherwise, ObjectDB may search and register all the entity classes in the classpath. support Support |
6 | Adding indexes on existing entities. the classpath. Update: Starting ObjectDB 2.6.6 new indexes are automatically built and activated in |
6 | New to Product & Having An Issue. But if you add your DomainId class to the server classpath it should work. Anyway, = is more efficient |
6 | NoSuchFieldError: __odbTracker on NetBeans 7.3 + JBoss 7.1.1="com.objectdb.Enhancer" fork="true" classpath="C:/projects/test/lib/objectdb.jar"> <arg |
1 | javax.servlet.ServletException: Annotated methods must follow the JavaBeans naming convention. __odbHidden_getPropertyName and the old jar is not anywhere in the classpath. You are not using classes that have been enhanced by |
