Internal Website Search

may be thrown if you mix old and new enhancement . Please make sure that after the change you only use a clean build of your application with fresh enhancement . support Support Thanks, though I've been using this enhancement for ages (I think it's actually means no enhancement , serialization only): dmoshal

. galandor Orlov Sergey This exception indicates a missing enhancement , i.e. City is enhanced but its super class AbstractMethod is not enhanced . It is indeed weird that the problem is only with City ... and then redeployment solve the problem. You may also try using build time enhancement

Hi,    Just thought I'd share a small bit of Maven config to aid in enhancing persistent ... ;              com.objectdb. Enhancer     ... -plugin:1.2:java (default) @ project-domain --- [ObjectDB 2.2.2 Enhancer ] 4 persistable types

the system complains: [ObjectDB 2.8.0_04] javax.persistence.PersistenceException Type au.Person is not enhanced ( enhance the type or enable reflection)  (error 304)     at com.objectdb.jpa ... getting an error regarding enhancement - is this because I'm using openjdk version "1.8.0_212

that your persistence capable (entity) classes are not enhanced . ObjectDB supports working with no enhancement as an extension to JDO - but it is less efficient and has some limitations. For example, strong ... cannot be evicted. If your classes are not enhanced - enhancing them could solve the problem without any

java:jboss/datasources/PG Perhaps this is because of Enhancer , how can we disable it in this case ... . 

Looking forward to your response
 galandor Orlov Sergey This could happen due to partial enhancement , i.e. all the project is enhanced , but then specific classes are compiled again without enhancement

the enhancer (error 108) 13:49:37,705 ERROR [stderr] (MSC service thread 1-3) com.objectdb.o.UserException: Package guest is not found by the enhancer 13:49:37,706 ERROR [stderr] (MSC service thread 1 ... .o.JEN.k(JEN.java:90) 13:49:37,708 ERROR [stderr] (MSC service thread 1-3) at com.objectdb. Enhancer

Hi  I was trying to enhance some of my classes and I got an error :  Failed to generate ... advance b bolo Boguslaw Fraszko one more thing ....  : how to increase Enhancer log level ??   ... there is output from enhancer [ObjectDB 2.0] 3 persistable types have been enhanced : test.MyEntity1 test.MyEntity2

.EMImpl.find(EMImpl.java:518) ~[na:na] btc_es BTC EmbeddedSystems It may indicate a partial enhancement ... and enhancement of all the classes. support Support Good morning, Without enhancing any entities, we get the error mentioned in first post. When we enhance all entities, we get the following error instead: java

, that we have properly enhanced classes although it seems to me, that we  aren't using a best practise solution ... it we are using following code: String allString = getAllPackagesAsString(); Enhancer . enhance (allString); Output of enhancement before running the test was: [ObjectDB 2.8.3_05 Enhancer ] 553 persistable types

that creates my application (with ObjectDB Enhanced classes) but my application fails with the error ... and activations in recent versions. Please make sure that your classes are OEM enhanced . See this forum thread . support Support Thank you for the link to the class enhancing confirmation checking code. 

one entity have index on String column. Entities are not enhanced and inserts are committed in a separate ... ? 4410 Arsenii With enhanced classes you may get much better performance. Enhancement is very easy. For example, you can apply enhancement by: java -javaagent:c:\objectdb\bin\objectdb.jar

. These changes are detected if your classes are not enhanced . If your classes are enhanced ... to elements that are not detected in enhanced classes, correct? If a class variable is assigned a new value ... a (potentially identical) new value? kjkrum Kevin The behavior is different for enhanced classes and non

this used to work was that the Enhancer would not Enhance or sign the specified persistable classes ... .6 Enhancer ] 7 persistable types have been enhance How can I tell if a build does NOT occur ... activation code is available the message should be: [ObjectDB 2.7.6 OEM Enhancer ] rather than 

: enhance , phase: process-classes) pom.xml /Guestbook line 91 Maven Project Build Lifecycle Mapping ... -plugin 1.2 enhance process-classes java com.objectdb. Enhancer guest.Guest this is the error ... .codehaus.mojo:exec-maven-plugin:1.2:java (execution: enhance , phase: process-classes) pom.xml /mces line

have tried enhancing the jar, but did run into some trouble with this as well. Not sure whether enhancement is required? My code: @Entity public class Boat implements Serializable{ @Id private String name ... can identify it correctly with enhanced classes but not with classes that are not enhanced . Note

: Failed to get reference value of field field db.Point.x using enhanced method (error 613)    ... enhanced method     at com.objectdb.o._PersistenceException.a(_PersistenceException.java ... to get reference value of field field db.Point.x using enhanced method     at com.objectdb

the right version of the enhancer . There are no code errors. If I change everything back to 2.6.3 ... the enhancement is incomplete. Try to rebuild everything and run the Enhancer on all your entity ... of the enhancer : [ObjectDB 2.6.6 Enhancer ] 35 persistable types have been enhanced :    

that runs fine without enhancement but fails after classes are enhanced , see trace below. This line ... . ie: it seems that ObjectDB's enhancer adds __ to methods, which is incompatible with Quarkus's ... its own corner with several enhanced methods that start with "__odb". This will be taken into

.main(Main.java:1384) In an attempt to isoloate the problem I cleaned by project, and enhanced ... ; enhanceLabPlugin()     {         com.objectdb. Enhancer . enhance ... ()     {         com.objectdb. Enhancer . enhance ( '-s, J

a minimal test case that demonstrates the problem. support Support [ObjectDB 2.4.7_15 Enhancer ] 1 persistable type has been enhanced :     Person [ObjectDB 2.4.7_15 Enhancer ] 1 persistable type has been enhanced :     Test Stored: Ron After find and first lock: Ron

still not working: [ObjectDB 2.5.0 Enhancer ] 1 persistable type has been enhanced :     Association [ObjectDB 2.5.0 Enhancer ] 1 persistable type has been enhanced :     ... .NullPointerException at Test.main(Test.java:31) at Enhance .main( Enhance .java:6) import java.util.Map; import

that are supported by ObjectDB only for enhanced classes. For a class that is not enhanced ObjectDB ... is considered as transient. It is not practical to support it for non enhanced classes, without causing a memory leak. ObjectDB may be the only JDO implementation that supports non enhanced classes

numeric value of field field model.User.gid using enhanced method (error 362) at javax.swing ... .gid using enhanced method at com.objectdb.o.MSG.d(MSG.java:74) at com.objectdb.o.UMR.M(UMR.java:905 ... value of field field model.User.gid using enhanced method (error 362) at javax.swing.AbstractButton

the new ObjectDB build load time weaving ( enhancement ) by Spring is currently disabled ... ! Though i am pondering about the repercussions of spring enhancement not being applied. (as far as i ... dries Thank you for your useful report. You can still use ordinary enhancement (e.g. during build

. The enhancement is done in a gradle task. Unfortunatly this has to be done on a macos due to XCode ... forgot to disconnect the VPN connection there is no valid enhancement for the whole build for all different platforms. This will be recognized in the UAT after enhancing , building, notarisation, uploading

that the test works well also with previous builds when enhancement is used. So even though it is good ... enhanced classes (which are much more efficient). support Support This test case has been distilled from ... enhanced classes - we did try to use them, but it had it's own set of issues, so we moved back to plain

private long amount ; etc... }   Kevin Kevin Pfaff Questions: Are your classes enhanced ... been already loaded would be missing. support Support No, none are enhanced , neither serverside nor locally ... enhanced classes. First, it is usually much more efficient. Second, it uses a different mechanism

Hi I have created in Eclipse a new plugin from existing jar file and than I tried to enhance ... ] Package datamodel.core.base is not found by the enhancer (error 108) The Enhancer was run in ... ().loadClass("datamodel.core.base.NamedCoreObj").getClassLoader();       Enhancer

? lwalkowski Lukasz Walkowski Running the test case (with enhancer enabled) produces output that ends ... ; lwalkowski Lukasz Walkowski Running the new test with enhancement enabled produces: Store: 4, size: 9 ... : 94, store: 4 Offer: Offer for product: 84, store: 4 but with no enhancement - produces: Listing

? maybe you can use rollback or clear instead of commit? Do you always use only enhanced classes? With enhanced classes ObjectDB is not expected to hold strong references (which prevents garbage ... then we can do that instead. Thanks for this hint! Yes, only enhanced classes are used in this example

was not enhanced and caused the exceptions above. Although the enhancement check was activated: the enhancement check does not throw an objectdb exception. Have you an idea why the enhancement check does ... that you found the cause and thank you for the update.  Have you an idea why the enhancement check

Hi   there is something wrong with enhancement process I got that class was succesfully processed, log has size 0, enhancer is from build objectdb-2.2.8_08 and during object creation when some ... Tomasz Wozniak This might be the result of an incomplete enhancement - i.e. Network extends

of the enhanced Mitglied class. I am unable to replicate it in a simple testcase but it always happens in ... field version using enhanced method version is annotated with @Version quasado Alexander Adam Okay ... incomplete enhancement of the object model - i.e. some classes are enhanced and some other related classes

btc_es BTC EmbeddedSystems We have found a workaround. We have just enhanced the entities and then it works as intended. But why this case does not perform without enhanced entities? btc_es BTC EmbeddedSystems The exception may be due to having partial enhancement . Mixing enhanced entity classes

Enhancer modifies the names of persistent property  get and set methods by adding __odbHidden ... that. If this doesn't help maybe the Enhancer has to move the annotations to the proxy methods ... is not anywhere in the classpath. You are not using classes that have been enhanced by an older

this check is not needed when entity classes are enhanced , so enhancing the class may solve the issue. Note that mixing enhanced and non- enhanced classes is not supported and may cause various issues, so double check that all your entity classes are enhanced . Something else to check is that all objects

; em.close();     I also tried upgrading to 2.2.9_05. Now when I try to enhance I ... . Enhancer . enhance ( Enhancer .java:66) at com.objectdb. Enhancer . enhance ( Enhancer .java:87) at com ... ( enhancer ) exception in build 2.2.5_05 is caused by using the new build with an older configuration file

.btc.ep.formalnotation.bl.internal.dmos.PhaseImpl is not enhanced ( enhance the type or enable ... .UserException: Type com.btc.ep.formalnotation.bl.internal.dmos.PhaseImpl is not enhanced ( enhance the type or ... ( enhanced ) entity class in your project for that obsolete entity class. support Support

JDO Method in javax.jdo.listener.StoreCallback void jdoPreStore () Called before the values are stored from this instance to the data store. Data store fields that might have been affected by modified non-persistent fields should be updated in this method. This method is modified by the enhancer

JDO Interface LoadCallback This interface is used to notify instances of load events. Since: JDO 2.0 Public Methods void jdoPostLoad () Called after the values are loaded from the data store into this instance. This method is not modified by the enhancer . Derived fields should be initialized in

JDO Method in javax.jdo.listener.LoadCallback void jdoPostLoad () Called after the values are loaded from the data store into this instance. This method is not modified by the enhancer . Derived fields should be initialized in this method. The context in which this call is made does not allow

after this call are disallowed. This method is modified by the enhancer so that fields referenced can be used in the business logic of the method. Since: JDO 2.0

is modified by the enhancer so that fields referenced can be used in the business logic of the method. Since: JDO 2.0

and others in the runtime environment should be cleared. This method is not modified by the enhancer

JDO Method in javax.jdo.listener.ClearCallback void jdoPreClear () Called before the values in the instance are cleared. Transient fields should be cleared in this method. Associations between this instance and others in the runtime environment should be cleared. This method is not modified by the enhancer . Since: JDO 2.0

modified by the enhancer , so access to fields is not mediated. Parameters: event - the clear event. Since: JDO 2.0

the runtime environment should be cleared. This method is not modified by the enhancer . Since: JDO 2.0

JDO Interface StateInterrogation This interface is implemented by a non-binary-compatible JDO implementation to provide state interrogation for non- enhanced persistent classes. A call to JDOHelper to get the status of an instance is handled internally if the parameter instance implements

identity. It is intended only for application identity. If the class has been enhanced