openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Blevins (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OPENJPA-919) JUnit for Bi-directional OneToOne with null relationships
Date Wed, 11 Feb 2009 03:54:59 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Blevins updated OPENJPA-919:
----------------------------------

    Attachment: jpa-nullrelation.tar.gz

Here's a test case that reproduces what I'm seeing.  Like the custom id issue this test case
passes if the relation names are changed, proving that there is some sort of case sensitive
or sorting issue with the fields in the bean.  Rename the 'C' fields to 'c' and the test will
pass.

> JUnit for Bi-directional OneToOne with null relationships
> ---------------------------------------------------------
>
>                 Key: OPENJPA-919
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-919
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: jdbc
>    Affects Versions: 1.2.0, 1.3.0, 2.0.0
>            Reporter: Donald Woods
>            Priority: Trivial
>             Fix For: 1.2.1, 1.3.0, 2.0.0
>
>         Attachments: jpa-nullrelation.tar.gz, OPENJPA-919-branches12x.patch, OPENJPA-919-branches13x.patch,
OPENJPA-919-trunk.patch
>
>
> Testcase to verify relationships in a bi-directional OneToOne are null (as tested for
by the EJB TCK) when:
> 1) the relations are not set (should default to null)
> 2) the relations are explicitly set to null

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message