6 | Error when using Object DB Java Agent code is built with maven and the classes are compile time enhanced. With the agent we have a problem |
6 | How to use ObjectDB properly in spring boot application? (embedded) Maven Uses annotation based configuration (no xml file) A dummy entity class (e.g: Customer |
6 | Problem on JPA Merge Entity. Support Hi, My apologies, in fact I did not change the version in the configuration file of maven |
6 | UTF Error trace. support Support The Client side is 2.8.8 (a maven project) . The downloaded version |
6 | PostUpdate on array changes, regardless of JUnit. > How can I pre-enhance classes with Gradle? A Maven and an Ant enhancement |
6 | Eclipse4 RCP - No Persistence provider for EntityManager also after build 2.6.2_02. It is not available on Maven but if you download ObjectDB you can find |
6 | OEM license, enhancerWe do have an OEM license. Ig I understand correctly, we do not have to create an activation code for each customer system when we are using enhancer. As we want to ship a standard database with the system which was created before having the OEM license and before adding enhancer to our maven |
6 | Problem undeploying Glassfish3.1.1 web application cleanly @PersistenceContext EntityManager injection)? Could not build GuestBook example from Maven, but I |
1 | ObjectDB 2.2.6 an error message for invalid query parameter (issue @320). Fixed pom.xml files in the Maven tutorials to use Java 1.5 / 1.6. |
1 | ObjectDB 2.2.3Added support of @ElementCollection (for setting eager fetch of non entity collections, such as List<String>). Improved performance of eager fetch in queries. Added Maven build enhancement to the bundled examples. Fixed a schema evolution bug in renaming user types. Fixed a bug in handling schema |
