ObjectDB ObjectDB

Internal Website Search

71-80 of 200 resultsRefresh

WebService : Failed to get reference value of field using enhanced method

de.tud.stg.emergent.policy.persistence.PolicyEntity.policyString using enhanced method at org ... enhanced method at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531 ... get always this error : "Failed to get reference value of field using enhanced method" . ClassCast error

OEM enhancing

Hello, I have question regarding OEM licence enhancement. @OneToMany(fetch = FetchType.EAGER ... >(); Are these classes(SomeClass, SomeClass2), when not enhanced, limited by number 1 million instances in ... they should be enhanced to avoid the restriction of one million instances in the database (on end user machines). support Support

Not Enhanced: ...: com.objectdb.o.TEX: Type ..._$$_javassist_1 is not found

enhancement. As you noted, this class is not related to ObjectDB and does not need enhancement ... this exception, or decrease the logging level of this ObjectDB component to ERROR: <logger name="enhancer

Suggest link to Maven example from Enhancer tool page

The maven plugin example here is incomplete: https://www.objectdb.com/java/jpa/tool/enhancer#Maven_and_ANT_Enhancement_ Taken literally it can't work because it's missing this: <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <version>1.2</version

JDO PersistenceCapable Interface for Enhanced Classes

) model); the interface was enhanced to the class. in the new version we get this java.lang ... , and the ObjectDB 2.x Enhancer does not implement that interface. You should remove the casting

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 ... but it is inconvenient to have to remove generic loops just because of enhancement: for (Object os

Enhancer NullPointerException

I'm getting the following stack trace when running the enhancer on one of my jars: [ObjectDB 2.3.2_04] null java.lang.NullPointerException at com.objectdb.o.JEL.L(JEL.java:633 ... .objectdb.Enhancer.main(Enhancer.java:32) Please let me know if you need any further information

Feature suggestion: Improved Maven Enhancer support

There may a way to achieve recursive application of the enhancer using the maven plugin approach ... >com.objectdb.Enhancer</mainClass>        <!-- List of your packages -->        <arguments ... can be scanned automatically and enhanced if necessary. support Support

Enhancer API (JDO 3.0)

One of the new features of JDO 3 is a standard API for enhancement. Currently ObjectDB implements its own enhancement API. support Support

Activation & Object Model Enhancement

We'd like to buy and use OEM Licenses. However, our object model gets enhanced at runtime (using JEnhancer directly) and not at compile time so we can not "sign" our object model at compile time ... that calls JEnhancer that then enhances the object model correctly at runtime? See, we don't have any

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