You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@openjpa.apache.org by "Guillaume Chauvet (JIRA)" <ji...@apache.org> on 2013/03/22 18:33:15 UTC

[jira] [Created] (OPENJPA-2357) @..ToMany(optional=false) throws InvalidStateException: [...] the metadata for this field specifies that nulls are illegal.

Guillaume Chauvet created OPENJPA-2357:
------------------------------------------

             Summary: @..ToMany(optional=false) throws InvalidStateException: [...] the metadata for this field specifies that nulls are illegal.
                 Key: OPENJPA-2357
                 URL: https://issues.apache.org/jira/browse/OPENJPA-2357
             Project: OpenJPA
          Issue Type: Bug
          Components: kernel
    Affects Versions: 2.2.1, 2.2.0
            Reporter: Guillaume Chauvet
            Priority: Critical


Hi,

We have discovered a bug in OpenJPA when InverseManager is used with collection annoted @toMany([...], optional = false). OpenJPA doesn't solve inverse relation before calling here internal preflush method.

This bug does not exist on 2.1.0 and 2.1.1.

A unitary test and a small patch is worth a thousand words ;) [1]

[1] Patch successfully tested on OpenPJA 2.2.1 and in our software.

Regards,


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira