ObjectDB ObjectDB

Internal Website Search

71-80 of 200 resultsRefresh
75

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
75

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
75

@Enhancement annotation

Hi, We've found out that ObjectDB has its own annotation called @Enhancement which can be applied to non-persistent classes (with format (enabled = false)), so that they are not enhanced at all. We found this annotation by accident and proved its behaviour via tests, but did not find any
73

How to enhance the JPA/Spring/MVC to implement RESTfull for CURL client?

Here is my attempt to enhance the JPA/MVC/eclipse tutorial to implement a RESTful service. Why does this not work with this curl command? I get 404. Can someone help me correct this? Do I need to change my web.xml servlet mapping in web.xml? I've been experimenting with and nothing seems to work
15

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
15

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
15

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
15

After using the enhancer, Lazy loaded collections are no longer loading. They are set as null

until running the enhancer on compiled jpa entities timbob1000 Tim Osborn Your issue cannot be reproduced ... that produces different results with and without enhancement. import java.util.*; import javax
14

java.lang.NullPointerException during access a field, only if the classes enhanced

We get the following exception during access a field (Set of entities) The error occurs only if the entities are enhanced. Caused by: com.objectdb.o.InternalException: Unexpected internal exception at com.objectdb.o.JPE.h(JPE.java:168) at com.objectdb.o.ERR.f(ERR.java:66
14

Database Management Settings

- you should only activate ObjectDB on developer machines. Classes that are enhanced by the ObjectDB Enhancer (when using the OEM license) are signed and excluded from evaluation restrictions. Therefore, when ObjectDB runtime is bundled in a product that uses only signed enhanced persistable classes - activation by end users is unnecessary.

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