Internal Website Search
11-20 of 200 resultsRefreshCascading (persist) with a mix of enhanced and not enhanced entities We 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? enhanced. To enhance the entities during development is, because of our build environment | |
Pre-detach loading: retrieval by navigation not working in if statement. Note that the main difference between build time enhancement and on the fly javaagent ... ;the main difference between build time enhancement and on the fly javaagent enhancement ... /1512#item-3">here: Automatic on the fly runtime enhancement | |
enhanced object .. NOT enhanced Hi I think I have found a bug : - I have enhanced ... expeption. b bolo Boguslaw Fraszko > I have enhanced a class but when I tried ... of no enhancement but of a missing @Entity / @PersistenceCapable | |
objectdb-2.6.9_02 (with "objectdb.temp.no-enhancement-crc-check") vs. generic classes with interfaces: detailed investigation objectdb-2.6.9_02 (with "objectdb.temp.no-enhancement-crc-check ... for "Enhancement of type ... is old and cannot be used" This report concerns investigation ... for the console app uses a post-compile, pre-deployment Ant script invoked using Clean and Build that enhances | |
Dependency from enhanced classes to the objectDB library Hello, we have a Question to the dependency from enhanced classes (required ... we get an error when we have enhanced the entities. java.lang ... only if we allow the usage of not enhanced classes. <entities> | |
Possible cause for "Enhancement of type ... is old and cannot be used":02 #1 type.user] Enhancement of type com.btc.ep.requirement.bl.internal ... type] Type com.btc.ep.requirement.bl.internal.ScopeRequirementContainerImpl is not enhanced. [2015-06-08 13:07:02 #3 type.user] Enhancement of type com.btc.ep.requirement.bl.internal | |
Updating JPA Entity Objects automatically is described in the enhancer">Enhancer section in chapter 5.enhanced. Therefore, for efficiency purposes, the default behavior of ObjectDB ignores array changes when using enhanced entity classes: Employee employee = em. | |
Step 3: Add a Context Listener Class the EntityManagerFactory & Enhance: public void contextInitialized(ServletContextEvent e) { com.objectdb.Enhancer.enhance("guest.*"); EntityManagerFactory emf ... above: Invokes the Enhancer to enhance the entity class, creates an | |
Step 3: Add a Context Listener Class { // Prepare the EntityManagerFactory & Enhance: public void contextInitialized(ServletContextEvent e) { com.objectdb.Enhancer.enhance("guest.*"); EntityManagerFactory ... (); } } The code above: Invokes the Enhancer to enhance the entity class | |
[ODB1] Chapter 6 - Persistent Objects, is done automatically by the JDO enhancer. Non persistent classes that directly access persistent fields ... through the JDO 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 |