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

Posted to dev@openjpa.apache.org by "Pawel Veselov (JIRA)" <ji...@apache.org> on 2018/09/03 12:29:01 UTC

[jira] [Created] (OPENJPA-2749) Broker can be used with mappings not synchronized

Pawel Veselov created OPENJPA-2749:
--------------------------------------

             Summary: Broker can be used with mappings not synchronized
                 Key: OPENJPA-2749
                 URL: https://issues.apache.org/jira/browse/OPENJPA-2749
             Project: OpenJPA
          Issue Type: Bug
          Components: jpa
    Affects Versions: 2.4.2
            Reporter: Pawel Veselov


If mapping synchronization fails once, then the next time creating a broker is attempted, it simply succeeds. This means running broker over problematic mappings, which is probably not cool.

JDBCBrokerFactory.newBrokerImpl(String, String) sets the "_synchronizedMappings" to true before calling the implementation, causing this. Setting the flag to true should be moved past the actual initialization call.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)