Internal Website Search
61-70 of 172 resultsRefreshA lot of ENT and SIV instances which are not cleared by GC classes? Are you using "objectdb.temp.no-detach"? Try ... > support Support Yes, I use no-detach option. So how can I fix it? Remove no-detach? But it has negative effects too. Vladiator Vlad Myachikov | |
Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct) activation is failing AND/OR: entities are becoming detached. http://www.objectdb.com/java/jpa/persistence/detach I can't find out how to test where an entity is detached.detachment might be the problem here. Try setting the fetch type of | |
makeTransientAll(pcs, useFetchPlan) detached; there is no detachment information in the instances. The instances to be made transient do not need to implement the javax.jdo.spi.Detachable interface. | |
makeTransient(pc, useFetchPlan)> Unlike detachCopy, the instances are not detached; there is no detachment information in ... .Detachable interface. Parameters: | |
makeTransientAll(pcs, useFetchPlan) detached; there is no detachment information in the instances. The instances to be made transient do not need to implement the javax.jdo.spi.Detachable interface. | |
preAttach(event)"> This method is called before a detached instance is attached, via the method. The source instance is the detached instance ... on the detached instance. | |
javax.jdo.listener.AttachCallback.jdo.PersistenceManager.makePersistent on the detached instance before the copy ... on the detached instance before the copy is made. | |
isDirty(pc) modified while detached return Boolean.TRUE . Instances known by ... while detached. Since: | |
postAttach(event)"> This method is called after a detached instance is attached, via the detached instance. This method is called | |
getDetachedInstance() getDetachedInstance() Returns the detached instance involved in ... > The detached instance involved in the event, or null if there was none. |