Internal Website Search

-maven-plugin 1.2 enhance process-classes java com.objectdb. Enhancer com.agile.hummingbird.Document ... Zwicker The classes are probably not enhanced with the OEM Enhancer . Please check if in the build ... is enhanced (OEM or not). com.objectdb.spi.SignedType - indicates that a class is OEM enhanced

Hello, is there any possibility for a check whether all entities are already enhanced within a jar file? We got following exception although we think all entities are enhanced : Caused by: com ... regards BTC btc_es BTC EmbeddedSystems Enhanced classes implement the interface  com.objectdb.spi

I have an entity library which I have integrated build time enhancement in.  The enhancer ... ) is listed as having been enhanced . I am running with ObjectDB in embedded mode via a reference ... This exception may be the result of partial enhancement . For example, enhancement of a super entity

I doubt this is an ObjectDB- enhancer problem, I am however reporting it in case anybody ... extends Element { On post-compile enhancement I get this error (as reported in the odb log file ... .objectdb. Enhancer .main( Enhancer .java:33) Caused by: java.lang.LinkageError: loader constraint violation

Hello, I've an OSGi environment and try to enhance Classes with Maven as it is described in ... other plugins. Is there a way to include classes in enhancement process? Thanks for your help ... .objectdb.o.JEL.A(JEL.java:442) at com.objectdb.o.JEN.k(JEN.java:93) at com.objectdb. Enhancer .main( Enhancer

are not enhanced , added items are doubled. Here is an example: @Entity public class Customer ... thing - items are also doubled, when the classes are enhanced and before merging the customer object a field is setted. Previous example can be used as a test case, only: 1. add enhancement

; at com.objectdb. Enhancer .main( Enhancer .java:33) Caused by: com.objectdb.o.UserException: Failed ... .2_02 and the following enhancement config in gradle works: task enhance ( type: JavaExec ) {   main = 'com.objectdb. Enhancer '   classpath = sourceSets.main.runtimeClasspath   args '-cp

ObjectDB support wrote elsewhere: ... you do not need the Enhancer agent, since you use build time ... to disable the enhancer agent ... Q: Does run time enhancer due to GlassFish/Payara do anything that would affect loaded compile-time enhanced entity classes (other than just logging, typically just

Hello, is there a way/tool how to check whether build classes were enhanced with valid OEM license? Scenario: 1) Build and enhance Java application with some Object DB license key. 2) Pick particular JAR containing enhanced classes from the build above. 3) Run some tool against picked JAR

I have recently moved to post-compile enhancement (from automatic run-time enhancement ) using ... the enhancer on entity files. For full project build the following works, by grouping entities under clearly named packages: But the following for per-file post-compile enhancement also invokes

.8_06 All our entities are enhanced . There are nested entities in following hierarchy: @Entity ... a mismatching enhancement , but it could be anything. support Support Hello, First of all thank ... of the database). We see no connection between the database and the enhanced classes

Hi, I have the following test class that is failing when the enhancer is enabled, resulting in the error 'Failed to write the value of field field TestEmbeddableMap$MyAttributeItem.id using enhanced method.', if I disable the enhancement the test works as expected, and returns the expected

Trying to run enhancement , I get:    [ObjectDB 2.5.5_05] Invalid file type for enhancement : /home/steve/java/spiffymap-svn/sealog-core/build/classes/com/spiffymap/sealog/model/Audit.java (error 104) com.objectdb.o.UserException: Invalid file type for enhancement : /home/steve/java

to our customers. Therefore we think we need to test the enhanced classes. But that distorts our test ... "coverage" of our tests? btc_es BTC EmbeddedSystems Enhancement adds code to persistent classes ... that is added by enhancement . A simple solution could be to check test coverage with classes that are not

enhancer .sh build/libs/asli-cloudai.jar [ObjectDB 2.8.5_03] Failed to process class file of type 'io ... .objectdb.o.JEN.g(JEN.java:103) at com.objectdb. Enhancer .main( Enhancer .java:33) Caused by: java.lang ... .lang.ClassLoader.loadClass(ClassLoader.java:522) ... 10 more eko EKO FAJAR Enhancement requires

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 ... that have been enhanced by the Enhancer in OEM mode (i.e. with an OEM activation key), your software can access

whether enhancement has been applied to a wide range of classes, many of which have nothing to do with the entity layer. For example, it is checking whether PrimeFaces JSF toolkit classes are enhanced . I am using Maven-based compile-time enhancement applied to entity modules (only), so I know these checks

Just wondering if it's possible to add enhancement in the gradle build file after compilation ... David Moshal The following seems to work: task enhance (type: JavaExec) {   main = 'com.objectdb. Enhancer '   classpath = sourceSets.main.runtimeClasspath   args '-cp', 'src/main/groovy

After updating some of my code to java 8, enhancement threw "unexpected" exceptions from ... have been related to the java 8 update. In any event, my enhancement problem went away when I ... , but the project has to be rebuilt and enhanced again if the classes were enhanced with an earlier version

entries of my ArrayLists with embedded entities are missing. I've hunted the problem down to an enhanced ... ; public static void main(String[] args) {     // enhance entities     com.objectdb. Enhancer . enhance ("objectdbsscce.*");         // open db  

transformers on the classpath. This is normaly not a problem because the ObjectDB enhancer ignores non @Entity or already enhanced classes but in conjunction with new Java 8 class files it throws ... .5_01. mosi0815 Ralph Moser The new error is not related to the Enhancer fix, but to another fix

de.tud.stg.emergent.policy.persistence.PolicyEntity.policyString using enhanced method at org.apache ... of field field de.tud.stg.emergent.policy.persistence.PolicyEntity.policyString using enhanced method ... to get reference value of field using enhanced method" . ClassCast error was only once by me... --- I

Hello, I have question regarding OEM licence enhancement . @OneToMany(fetch = FetchType.EAGER ... enhanced , limited by number 1 million instances in DB? Thanks Marta   Maruta M Sedlakova If SomeClass and SomeClass2 are entity classes they should be enhanced to avoid the restriction

ArrayList();     models.add((PersistenceCapable) model); the interface was enhanced ... implementing the  javax.jdo.spi.PersistenceCapable is optional, and the ObjectDB 2.x Enhancer

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:                             org.codehaus.mojo

enhancement . As you noted, this class is not related to ObjectDB and does not need enhancement

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

Hello Support, I run on a prod server an objectdb java agent with my app. In this application, all my entities beans are constructed from a JAXBContext ( SOAP CXF Webservice or Direct JAXB Unmarshalling ) When i watch the objectdb log, i see pages of errors. Not Enhanced : com/test/MyBean

interpreter as well. Have you tried build time enhancement instead of using -javaagent? Please post relevant byte code after enhancement . support Support  Have you tried build time enhancement ... out how to get the compile-on-save feature of NetBeans to "play nice" when using per-file ObjectDB enhancement (as

to be smaller. During enhancement of the  SignalValueImpl class field originalValue was the 4th field. Assuming that there may have been a schema change since that enhancement rebuilding the project and enhancing all classes again may solve the issue. If it doesn't please upload the embedded

I added the class enhancer to my build script and I get the expected output of a list with the enhanced classes. Now if I try to deploy my created application I get the following error: Caused by ... a @MappedSuperclass. Without the enhancement everything works fine. Regards Kevin Kevin Kevin Pfaff Enhancement

Hi , I got this error when trying to enhance   Thanks --   bmpccdeMac-mini:CloudAI eko$ bash ~/lib/objectdb-2.8.4/bin/ enhancer .sh build/libs/asli-cloudai.jar [ObjectDB 2.8.4] Unexpected ... . Enhancer .main( Enhancer .java:33) eko EKO FAJAR Thank you for this report. Please try build 2.8.5_03

Element I encounter ObjectDB enhancement errors: private boolean loaded = false; @Transient @Override ... ) { this.loaded = loaded; } No matter whether using javaagent run-time enhancement or post-compile enhancement ... entity): INFO: [2014-11-23 16:54:03 #2 type] Type com.example.entity.Element is not enhanced

Hello! When the JPA entities are not enhanced the removal of an entry from a @OneToMany collection ... .getChildEntityContainer().remove("01"); does not work correctly with not enhanced JPA entities. package ... you for this report. It represents an issue with non enhanced classes, but it is not related to @OneToMany collection

Hello, we have found that the enhancer returned an non-zero exit code on errors. You can change this so that the error of the enhancers can be detected. btc_es BTC EmbeddedSystems Thank you for this report. Starting build 2.6.1_04 the Enhancer exits with non zero code on errors. Note

There may a way to achieve recursive application of the enhancer using the maven plugin ... .objectdb. Enhancer                  ... plugin. Maybe all the class files in the target directories can be scanned automatically and enhanced if necessary. support Support

I'm getting the following stack trace when running the enhancer on one of my jars: [ObjectDB 2.3.2_04] null java.lang.NullPointerException at com.objectdb.o.JEL.L(JEL.java:633) at com.objectdb.o.JEL.D(JEL.java:491) at com.objectdb.o.JEN.k(JEN.java:95) at com.objectdb. Enhancer .main( Enhancer .java:32

I 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 ... to have to remove generic loops just because of enhancement : for (Object os : steelMaterials.getL_Steel

One of the new features of JDO 3 is a standard API for enhancement . Currently ObjectDB implements its own enhancement API . support Support

; Note:  This scenario was working until running the enhancer on compiled jpa entities   ... with and without enhancement . import java.util.*; import javax.persistence.*; public class T1535 {   

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 ... our class that calls JEnhancer that then enhances the object model correctly at runtime

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) at com.objectdb.o

ArrayIndexOutOfBoundsException with enhanced Entity

. There is an Ant script with post-compile enhancement of all entity classes. When you clean and build it will report: Java/JVM version: 1.8 Java/JVM detail version: 1.8.0_74 ObjectDB enhancer : begin: (all classes within entity packages): javac.classpath:lib/objectdb-2.6.9.jar [ObjectDB 2.6.9 Enhancer ] 8

the enhancer . Derived fields should be initialized in this method. The context in ... should be cleared. This method is not modified by the enhancer . Inherited from: ClearCallback ... the enhancer so that fields referenced can be used in the business logic of the method. Inherited

, object identity, and version if it has one. In the Reference Implementation, the JDO Enhancer modifies ... . The Reference Enhancer also adds code to implement the methods defined by PersistenceCapable ... for JDO identity. It is intended only for application identity. If the class has been enhanced

identity; newObjectIdInstance(Class, Object) should be used instead. If the class has been enhanced

instead. If the class has been enhanced for datastore identity, or if the class is abstract, null

should be updated in this method. This method is modified by the enhancer so that changes to persistent