ObjectDB ObjectDB

Internal Website Search

191-200 of 200 resultsRefresh
7

Mysterious "Attempt to persist a reference to a non managed instance" error

com.objectdb.Enhancer; public class ODBTest { public static void main(String[] args) {     Enhancer.enhance("failing.*");       EntityManagerFactory emf = Persistence
7

Failed to read the value of field ... using reflection

.UMR.YU(UMR.java:607) ... 80 more btc_es BTC EmbeddedSystems It may indicate partial enhancement. As you use enhanced classes, make sure that all persistable classes are enhanced as well as
7

Soft Reference Object Cache Recommendation

heap size (4MB) than reported by you when running the test. Assuming you used enhanced classes (as ... ObjectDB (at leased when the test classes are enhanced). Still it is not released on GC ... is using enhanced classes and inspecting RAM is done after commits, not during. The JVM can make
7

Possible issue with LAZY Loading

. This happens, for example, when ObjectDB uses reflection mode (classes are not enhanced). In your example, the lazy location collection is loaded eagerly even when the classes are enhanced ... ; } and enhance the classes - the test will throw NullPointerException as expected because of an attempt to use
7

LAZY @ManyToOne field functions as EAGER

and ManyToOne relationships only in enhanced classes. If you run your test as recommended with enhancement enabled, e.g. java -javaagent:objectdb.jar com.greensoft.objectdb.test.console ... enhanced, ObjectDB has to ignore lazy loading and load "to-one" relationships eagerly
7

What role is the JDO in ObjectDB?

. It required vendors to enhance the bytecode of domain objects to produce class files that were binary ... and that its reliance on bytecode enhancement caused it to be unfairly stigmatized. This was probably true ... community that now thinks nothing of using frameworks that make extensive use of bytecode enhancement
7

Embedded & Activation & Scalation

and do enhance them at runtime, not compile time.. ? Alex quasado Alexander Adam Multiple processes ... , but this has not been scheduled for implementation yet. The object model is signed during enhancement, so the enhancement has to be performed before deployment (at compile time). This works well for existing
7

Unexpected NoSuchFieldError exception

Try rebuild and enhance of all your classes, as the error messages indicates a broken enhancement (e.g. some classes in a class hierarchy are enhanced some are not, which is not allowed). support Support
1

Another NPE on em.createQuery(query).getResultList()

objectdb.jar into your local repository). kaosko Kalle Korhonen It seems as a bug in using non enhanced ... that should fix it. If it doesn't work try using enhanced classes (you should use enhanced classes
1

ODB-FileWriter holds unecessary entity reference after transaction and entity manager are closed

that all your classes are enhanced. The screenshot indicates using some entity objects (MappingImpl?) in ... Support Thank you very much for your hint. If we enhance all entities then it works. btc_es BTC ... to entities although it is not needed. We did following: All entities are enhanced. The entity

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