About properties

api-jpa

JPA Annotations for Access Modes

Reference (JavaDoc) of JPA 2 access mode annotations, including @Access and AccessType (enum).... be accessed by JPA directly (as fields) or indirectly (as properties and get/set methods). JPA 2 provides an annotation and an enum for ...

 
api-jdo

javax.jdo.annotations.NullValue

Enumeration of the "null-value" behavior values.(Enum of JDO)

 
api-jdo

FetchGroup.members

Members (fields and properties) of the fetch group.(Annotation Element of javax.jdo.annotations.FetchGroup)

 
api-jpa

EntityResult.fields

Maps the columns specified in the SELECT list of the query to the properties or fields of the entity class.(Annotation Element of javax.persistence.EntityResult)

 
api-jpa

javax.persistence.JoinTable

Used in the mapping of associations.(Annotation of JPA)

 
api-jpa

javax.persistence.MapKeyClass

Specifies the type of the map key for associations of type java.util.Map.(Annotation of JPA)

 
api-jpa

ManyToOne.targetEntity

(Optional) The entity class that is the target of the association.(Annotation Element of javax.persistence.ManyToOne)

 
api-jpa

AttributeOverrides.value

(Required) One or more field or property mapping overrides.(Annotation Element of javax.persistence.AttributeOverrides)

 
forum_thread

How find out ObjectDB version at runtime (in a web app)

Am getting inconsistent results with the "objectdb.temp.no-enhancement-crc-check" system property of objectdb-2.6.9_02 in a Glassfish web app. Can see correct version of objectdb-2.6.9_02 in /build/web/WEB-INF/lib. When one runs the enhancer (which I am doing post-compile, pre-deploy with an Ant script) Object clearly indicates the version. Q: How can one interrogate objectdb for the version at run-time ? #1 2016-08-22 17:07 Am getting inconsistent results with the "objectdb.temp.no-enhancement-crc-check" system property of obj ...

 
issue

Sometimes the ObjectDB throws an internal expeption if a find() was executed

Sometimes the ObjectDB throws an internal exception if a find() was executed. It is a sporadic issue that occurs only with Objectdb 2.7.0_b2 and only if the entites are enhanced. (We don't enabled the new property "objectdb.temp.extended-ref-retrieval" from http://www.objectdb.com/database/forum/1161) With the previous version (2.7.0_b1) we don't get the exceptions. Two stack traces we observed: Bug Version: Priority: Critical Status: Fixed Replies: 1 Type:  Bug ...