Home » jdo2-tck-2.3-ea-src » org.apache.jdo.tck » mapping »

org.apache.jdo.tck.mapping

Classes:

AbstractRelationshipTest     code | html
CompletenessTest   Title:Completeness Test
Keywords: mapping
Assertion ID: A18.[not identified]
Assertion Description:  
code | html
CompletenessTestJPA   Title:Completeness Test JPA
Keywords: mapping
Assertion ID: A18.[not identified]
Assertion Description:  
code | html
CompletenessTestList   Title:Completeness Test List
Keywords: mapping
Assertion ID: A18.[not identified]
Assertion Description:  
code | html
CompletenessTestMap   Title:Completeness Test Map
Keywords: mapping
Assertion ID: A18.[not identified]
Assertion Description:  
code | html
CompletenessTestOrder   Title:Completeness Test for the Order model
Keywords: mapping compound identity
Assertion ID: A5.4.1-5
Assertion Description: Compound identity is a special case of application identity. 
code | html
Relationship1To1AllRelationships   Title:Relationship1To1AllRelationships
Keywords: mapping, managed relationships
Assertion ID: A15.3-14
Assertion Description: Regardless of which side changes the relationship, flush (whether done as part of commit or explicitly by the user) will modify the datastore to reflect the change and will update the memory model for consistency... 
code | html
Relationship1To1NoRelationships   Title:Relationship1To1NoRelationships
Keywords: mapping, managed relationships
Assertion ID: A15.3-14
Assertion Description: Regardless of which side changes the relationship, flush (whether done as part of commit or explicitly by the user) will modify the datastore to reflect the change and will update the memory model for consistency... 
code | html
Relationship1ToManyAllRelationships   Title:Relationship1ToManyAllRelationships
Keywords: mapping, managed relationships
Assertion ID: A15.3-14
Assertion Description: Regardless of which side changes the relationship, flush (whether done as part of commit or explicitly by the user) will modify the datastore to reflect the change and will update the memory model for consistency... 
code | html
Relationship1ToManyNoRelationships   Title:Relationship1ToManyNoRelationships
Keywords: mapping, managed relationships
Assertion ID: A15.3-14
Assertion Description: Regardless of which side changes the relationship, flush (whether done as part of commit or explicitly by the user) will modify the datastore to reflect the change and will update the memory model for consistency... 
code | html
RelationshipManyToManyAllRelationships   Title:RelationshipManyToManyAllRelationships
Keywords: mapping, managed relationships
Assertion ID: A15.3-14
Assertion Description: Regardless of which side changes the relationship, flush (whether done as part of commit or explicitly by the user) will modify the datastore to reflect the change and will update the memory model for consistency... 
code | html
RelationshipManyToManyNoRelationships   Title:RelationshipManyToManyNoRelationships
Keywords: mapping, managed relationships
Assertion ID: A15.3-14
Assertion Description: Regardless of which side changes the relationship, flush (whether done as part of commit or explicitly by the user) will modify the datastore to reflect the change and will update the memory model for consistency... 
code | html
RelationshipNegative1To1Test   Title:RelationshipNegative1To1Test
Keywords: mapping, managed relationships
Assertion ID: A15.3-14
Assertion Description: Regardless of which side changes the relationship, flush (whether done as part of commit or explicitly by the user) will modify the datastore to reflect the change and will update the memory model for consistency... 
code | html
RelationshipNegative1ToManyTest   Title:RelationshipNegative1ToManyTest
Keywords: mapping, managed relationships
Assertion ID: A15.3-14
Assertion Description: Regardless of which side changes the relationship, flush (whether done as part of commit or explicitly by the user) will modify the datastore to reflect the change and will update the memory model for consistency... 
code | html