26 | @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 |
25 | 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 |
20 | Maven driven compile time ehnancement enhancement) was generated by the on the fly enhancement in the listener during run, and not by the Maven ... Hi, Just thought I'd share a small bit of Maven config to aid in enhancing persistent classes ... > </executions> <configuration> <mainClass>com.objectdb.Enhancer</mainClass |
5 | 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 |
5 | 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 |
4 | 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. |
4 | ArrayIndexOutOfBoundsException with enhanced EntityArrayIndexOutOfBoundsException with enhanced Entity |
0 | Step 1: Create a Maven Web Project> <id>enhance</id> <phase>process-classes</phase> <goals> <goal>java</goal> </goals> <configuration> <mainClass>com.objectdb.Enhancer</mainClass |
0 | Step 1: Create a Maven Web Project> <id>enhance</id> <phase>process-classes</phase> <goals> <goal>java</goal> </goals> <configuration> <mainClass>com.objectdb.Enhancer |
0 | [ODB1] Chapter 4 - JDO Metadata. The metadata is used first by the JDO Enhancer, and later by the JDO ... (possibly in a jar file). 4.1 JDO Metadata Files During JDO enhancement and later at runtime |
