ObjectDB ObjectDB

Internal Website Search

1-10 of 200 resultsRefresh

How prevent post-compile enhancement of non entity classes

I have recently moved to post-compile enhancement (from automatic run-time enhancement) using ... /objectdb.jar"/> <target name="-post-compile"> <echo message="begin ObjectDB enhancer"/> <java ... enhancer"/> </target> But the following for per-file post-compile enhancement also invokes

Post-compile enhancement fails when static Log4j 2.5 based logger used in Entity

{ On post-compile enhancement I get this error (as reported in the odb log file): [ObjectDB 2.6.3_04 ... for the post-compile enhancement the class path is: javac.classpath:lib/objectdb.jar:/usr/local ... comment out that static LOGGER variable init line, the error vanishes and post-compile enhancement

Post-compilation enhancement vs Automatic Run-time enhancement

We are getting massively different results on field loading between explicit post-compile ... on the fly runtime enhancement is applied only to entity classes, where post compilation enhancement ... of is now provided under forum posting: Pre-detach loading: retrieval by navigation not working in

Compile time enhancement using build.xml of a Netbeans web application

-post-compile and -post-compile-single. I do not see yet how to relate the manual's example ... : <target name="-post-compile">   <echo message="begin ObjectDB enhancer"/>    <java classname="com ... .jar has to be adapted.) However, I want to have a version of this that works with -post-compile

Posting Sample Code

To demonstrate a technical question or an issue - you may have to provide a complete runnable sample program. If an unexpected exception (e.g. NullPointerException or ClassCastException) is thrown by ObjectDB - posting the full stack trace with no sample program (using the Issue Tracking

Maven driven compile time ehnancement

during compile time. Just add the following to your pom.xml:  <build>   <plugins>    <plugin ... >compile</scope>      </dependency>         </dependencies>     <executions>      <execution>       <phase>compile</phase>       <goals>        <goal>java</goal>       </goals>      </execution

JPA / JDO Class Enhancer

ObjectDB Enhancer is a post compilation tool that improves performance by modifying the byte code of compiled classes after compilation. Enhancement is mainly for user-defined persistable classes ... file defines a Java compiler plugin that includes enhancement: <build> ...   <plugins

Post-compile enhancement sometimes causes error in generic loops: incompatible types found: java.lang.Object: required: Entity

I have moved from automatic run-time enhancement to explicit post-compile enhancement in an Ant build.xml in a NetBeans web app, and sometimes on editing a file that performs a generic for loop over an @entity type I get a generics error. The generic for loop is: for (Steel s: this.steelMaterials


Method javax.jdo.PersistenceManager Query newQuery( Object compiled ) Create a new Query using elements from another Query. The other Query must have been created by the same JDO implementation ... Extent. Parameters: compiled - another Query from the same JDO implementation Returns: the new Query Since: JDO 1.0


Method javax.jdo.Query void compile() Verify the elements of the query and provide a hint to the query to prepare and optimize an execution plan. 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