19 | Spring MVC Errors: "To enable on the fly automatic enhancement (weaving) in Tomcat it has to be run with ObjectDB as a Java agent (javaagent:objectdb.jar). When using GlassFish - on the fly enhancement (weaving ... configuration: org.codehaus.mojo:exec-maven-plugin:1.2:java (execution: enhance, phase: process |
13 | DB reading fails in debug mode in Eclipse) enhancement rather than on the fly enhancement. support Support ... Gergely Jakab The stack trace may indicate an incomplete enhancement. Try full clean build of your project with full enhancement of all your classes (particularly all persistence capable classes |
3 | NullPointerException in __odbGetNumMember other related classes (e.g. a super class) are not enhanced. If you enhance classes on the fly ... of the enhanced Mitglied class. I am unable to replicate it in a simple testcase but it always happens in ... value of field field version using enhanced method version is annotated with @Version quasado Alexander |
2 | ObjectDB 2.8 Developer's Guide ObjectDB Tools: the Explorer, the Enhancer, the Doctor, etc. Describes the ObjectDB configuration |
2 | FROM clause (JPQL / Criteria API)The FROM clause declares query identification variables that represent iteration over objects in the database. A query identification variable is similar to a variable of a Java enhanced for loop in a program, since both are used for iteration over objects. Range Variables Range variables are query |
2 | JPA Entity Fields 3) unless either the entity class is enhanced (explained in chapter 5) or a version field |
2 | Running JPA Queries an enhanced for loop: for (Country c : results) { System.out.println(c.getName()); } Note |
2 | database corrupt" /> <extensions drop="temp,tmp" /> </database> <entities> <enhancement agent="false" reflection="warning ... more information if needed. the 'on the fly' Doctor would be great for such sensible applications |
0 | JDO Annotations for ClassesJDO supports two modes of persistable classes that can be set by the following annotations: Non persistable classes that should be enhanced (because of accessing persistent fields of other classes directly) can be marked with: The identity mode of persistence capable classes can be specified by using: |
0 | javax.jdo.spi.PersistenceCapable PersistenceManager, object identity, and version if it has one. In the Reference Implementation, the JDO Enhancer ... environment. The Reference Enhancer also adds code to implement the methods defined by PersistenceCapable ... has been enhanced to call the jdoStateManager on read if the jdoFlags setting is not READ_OK or READ_WRITE_OK |
