Internal Website Search
61-70 of 121 resultsRefreshjavax.persistence.PersistenceException plugin. Adding objectdb.jar to the plugin runtime classpath. | |
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 class is not | |
Mismatch client-server protocol prefix. Also there's only one objectdb jar on the classpath. It's also not a network problem. It also happens on the node | |
Connection performace after upgrade to objectdb 2 and JDO metadata in the classpath (for synchronization with the database), and this could be optimized | |
Type xxx is not found (error 301).jar in your classpath before objectdb.jar - this happens for example if you use old Glassfish | |
EntityManager getMetamodel() causes crash classes in the classpath. support Support | |
Adding indexes on existing entities. (either annotation in class or xml), or run the Doctor with this available in the classpath. | |
New to Product & Having An Issue classpath it should work. Anyway, = is more efficient than | |
NoSuchFieldError: __odbTracker on NetBeans 7.3 + JBoss 7.1.1="true" classpath="C:/projects/test/lib/objectdb.jar"> <arg line="-s ./build | |
javax.servlet.ServletException: Annotated methods must follow the JavaBeans naming convention. __odbHidden_getPropertyName> You are using only the new ObjectDB jar and the old jar is not anywhere in the classpath. |