ObjectDB ObjectDB

Internal Website Search

131-140 of 200 resultsRefresh
12

Insert time increases as db grows.

have index on String column. Entities are not enhanced and inserts are committed in a separate ... ? 4410 Arsenii With enhanced classes you may get much better performance. Enhancement is very easy. For example, you can apply enhancement by: > java -javaagent:c:\objectdb\bin\objectdb.jar
11

Spring MVC Errors

configuration: org.codehaus.mojo:exec-maven-plugin:1.2:java (execution: enhance, phase: process ... > <id>enhance</id> <phase>process-classes</phase> <goals> <goal>java</goal> </goals> <configuration> <mainClass>com.objectdb.Enhancer</mainClass
11

Determining if Persistable Classes Have Trial Limitation

was that the Enhancer would not Enhance or sign the specified persistable classes without a valid key ... below which would seem to indicate success (classes not affected by trial limitations): [ObjectDB 2.7.6 Enhancer] 7 persistable types have been enhance How can I tell if a build does NOT occur with a valid key
10

Felix, rollback exception, error 613

to get reference value of field field db.Point.x using enhanced method (error 613) at com.objectdb.jpa ... .o.UserException: Failed to get reference value of field field db.Point.x using enhanced method ... : Failed to get reference value of field field db.Point.x using enhanced method at com.objectdb.o.MSG
10

Problem upgrading

the right version of the enhancer. There are no code errors. If I change everything back to 2.6.3 ... due to unknown reason), so maybe the enhancement is incomplete. Try to rebuild everything and run the Enhancer ... . That's the output of the enhancer: [ObjectDB 2.6.6 Enhancer] 35 persistable types have been enhanced
2

Unexpected Exception during commit

to enhance I get: java.lang.NullPointerException at com.objectdb.o.CFG.t(CFG.java:272 ... ) at com.objectdb.o.JEN.<init>(JEN.java:59) at com.objectdb.Enhancer.enhance(Enhancer.java:66) at com.objectdb.Enhancer.enhance(Enhancer.java:87) at com.fastmodel.fastplan.db
2

javax.servlet.ServletException: Annotated methods must follow the JavaBeans naming convention. __odbHidden_getPropertyName

handles __odbHidden_getWidthPxSideBarLeft. webel Dr Darren Kelly The ObjectDB Enhancer modifies ... the Enhancer has to move the annotations to the proxy methods, but that would be more difficult ... and the old jar is not anywhere in the classpath. You are not using classes that have been enhanced by
0

PersistenceCapable.MEDIATE_WRITE

Static Field javax.jdo.spi.PersistenceCapable byte MEDIATE_WRITE If jdoFieldFlags for a field includes MEDIATE_WRITE, then the field has been enhanced to always call the jdoStateManager on all writes. Since: JDO 1.0
0

javax.jdo.listener.StoreCallback

should be updated in this method. This method is modified by the enhancer so that changes
0

PersistenceCapable.MEDIATE_READ

Static Field javax.jdo.spi.PersistenceCapable byte MEDIATE_READ If jdoFieldFlags for a field includes MEDIATE_READ, then the field has been enhanced to always call the jdoStateManager on all reads. Since: JDO 1.0

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support