ObjectDB ObjectDB

Internal Website Search

111-120 of 200 resultsRefresh
2

ValidationMode.NONE

Enum Constantjavax.persistence.ValidationMode NONE The persistence provider must not perform lifecycle event validation. Since: JPA 2.0
2

ValidationMode.CALLBACK

Enum Constantjavax.persistence.ValidationMode CALLBACK The persistence provider must perform the lifecycle event validation. It is an error if there is no Bean Validation provider present in the environment. Since: JPA 2.0
2

ValidationMode.AUTO

Enum Constantjavax.persistence.ValidationMode AUTO If a Bean Validation provider is present in the environment, the persistence provider must perform the automatic validation of entities. If no Bean Validation provider is present in the environment, no lifecycle event validation takes place. This is the default behavior. Since: JPA 2.0
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
0

registerClass(pcClass, fieldNames, fieldTypes, fieldFlags, persistenceCapableSuperclass, pc)

the same or an ancestor class loader as the PersistenceCapable class performing the registration
0

javax.jdo.Transaction

to flushing instances to the data store. The afterCompletion method is called after performing state
0

checkAuthorizedStateManager(sm)

("setStateManager"). To improve performance, first the set of authorized classes is checked, and if not present
0

javax.jdo.datastore.JDOConnection

implementation prior to calling any JDO method or performing any action on any persistent instance
0

setSynchronization(sync)

after performing state transitions of persistent and transactional instances, following the data store commit
0

jdoNewInstance(sm, oid)

a performance optimization as an alternative to using reflection to construct a new instance of a class

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support