66 | Enhancement API - NullPointerException a jar file? On the fly enhancement by calling com.objectdb.Enhancer.enhance(...) is only supported ... Hi! I am trying to use the Enhancement API from within my application like this: com.objectdb.Enhancer.enhance("my.package.Foo"); However, I get the following NullPointerException: [ObjectDB 2.7.1 |
38 | Cascading (persist) with a mix of enhanced and not enhanced entitiesWe find out that it is actual not possible to use enhanced and not enhanced entities together. Exist any limitations regarding the use of enhanced and non-enhanced entities? We work based feature and want to load other bundles as an artifact from the Nexus. These are always enhanced. To enhance |
36 | Pre-detach loading: retrieval by navigation not working in if statement difference between build time enhancement and on the fly javaagent enhancement is that the later ... classes). support Support > the main difference between build time enhancement and on the fly javaagent ... on the fly runtime enhancement is applied only to entity classes, where post compilation enhancement |
36 | enhanced object .. NOT enhancedHi I think I have found a bug : - I have enhanced a class but when I tried to persitst it I got ... we get an OutOfMemory expeption. b bolo Boguslaw Fraszko > I have enhanced a class but when I tried to persitst ... serialization is not the result of no enhancement but of a missing @Entity / @PersistenceCapable |
36 | objectdb-2.6.9_02 (with "objectdb.temp.no-enhancement-crc-check") vs. generic classes with interfaces: detailed investigationobjectdb-2.6.9_02 (with "objectdb.temp.no-enhancement-crc-check" system property) The following ... value of field property Element.id using reflection - Possible cause for "Enhancement of type ... -compile, pre-deployment Ant script invoked using Clean and Build that enhances every entity class in |
33 | Dependency from enhanced classes to the objectDB libraryHello, we have a Question to the dependency from enhanced classes (required for license ... and to all domains, because there are the entities. Now we get an error when we have enhanced ... only if we allow the usage of not enhanced classes. <entities> <enhancement agent="false" reflection |
31 | Possible cause for "Enhancement of type ... is old and cannot be used"We get the following log: [2015-06-08 13:07:02 #1 type.user] Enhancement of type com.btc.ep ... .ScopeRequirementContainerImpl is not enhanced. [2015-06-08 13:07:02 #3 type.user] Enhancement of type ... .internal.RequirementReferenceImpl is not enhanced. We understand the reason of the messages #2 and #4 "Type |
9 | Chapter 5 - Database Tools and UtilitiesDescribes the ObjectDB object database tools - the Explorer, the Server, the Enhancer, the Doctor and the Replayer. |
7 | Enhancer option to enhance all persitable typesHello, can you add an option to the Class Enhancer to enhance all persistable types and ignore the NON persistable types. Like the Load Time Enhancement. btc_es BTC EmbeddedSystems A new argument (undocumented yet) was added to the Enhancer in build 2.6.2_06: > java -cp objectdb.jar com.objectdb |
0 | [ODB1] Chapter 6 - Persistent Objects by the JDO enhancer. Non persistent classes that directly access persistent fields of other classes ... enhancer, which enhances them to include the code needed for transparent persistence. But, because these classes are not described in the JDO metadata files, the enhancer identifies them as not |
