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.
Internal Website Search71-80 of 200 resultsRefresh
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
) 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
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
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
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
One of the new features of JDO 3 is a standard API for enhancement. Currently ObjectDB implements its own enhancement API. support Support
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
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
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
- 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.