2 | Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct). For a number of different List fields, a query performed immediately after creating and persisting many Element objects gives expected results, but the same query performed later form a served JSF page ... of createData() I perform an echoed query on all elements and interrogate the ownedElements list |
2 | transform(loader, className, classBeingRedefined, protectionDomain, classfileBuffer) if no transform is performed Throws: IllegalClassFormatException - if the input does not represent a well-formed class file Since: JPA 1.0 |
2 | javax.persistence.spi.ClassTransformer: a well-formed class file buffer (the result of the transform), or null if no transform is performed Throws |
2 | find(entityClass, primaryKey, lockMode, properties) is pessimistic and the entity has a version attribute, the persistence provider must perform optimistic version |
2 | as(type)Method javax.persistence.criteria.Expression Expression<X> as( Class<X> type ) Perform a typecast upon the expression, returning a new expression object. This method does not cause type conversion: the runtime type is not changed. Warning: may result in a runtime failure. Parameters: type |
2 | InheritanceType.JOINEDEnum Constant javax.persistence.InheritanceType JOINED A strategy in which fields that are specific to a subclass are mapped to a separate table than the fields that are common to the parent class, and a join is performed to instantiate the subclass. Since: JPA 1.0 |
0 | checkAuthorizedStateManager(sm)("setStateManager"). To improve performance, first the set of authorized classes is checked, and if not present |
0 | javax.jdo.Transaction to flushing instances to the data store. The afterCompletion method is called after performing state |
0 | close()Method javax.jdo.datastore.JDOConnection void close() Returns this connection to the JDO implementation. The object must be returned to the JDO implementation prior to calling any JDO method or performing any action on any persistent instance that might require the JDO implementation to use |
0 | setSynchronization(sync) after performing state transitions of persistent and transactional instances, following the data store commit |
