82 | OEM enhancingHello, 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 |
81 | 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 |
81 | Suggest link to Maven example from Enhancer tool pageThe 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 |
81 | @Enhancement annotationHi, 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 |
79 | 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 |
16 | Post-compile enhancement sometimes causes error in generic loops: incompatible types found: java.lang.Object: required: EntityI 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 |
16 | 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 |
16 | 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 |
16 | Activation & Object Model EnhancementWe'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 | java.lang.NullPointerException during access a field, only if the classes enhancedWe 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 |
