[
https://issues.apache.org/jira/browse/OPENJPA-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim McConnell updated OPENJPA-1237:
-----------------------------------
Attachment: OPENJPA-1237-2.patch
This second patch includes testcases to ensure that the appropriate
WriteBehindConfigurationException is thrown for invalid configurations and an
EntityManagerFactory is instantiated for valid configurations. Also, it will
now properly throw a WriteBehindConfigurationException in all cases where
required WriteBehind configuration parameters are omitted.
> WriteBehind configuration exception not thrown when it should be
> ----------------------------------------------------------------
>
> Key: OPENJPA-1237
> URL: https://issues.apache.org/jira/browse/OPENJPA-1237
> Project: OpenJPA
> Issue Type: Bug
> Components: kernel
> Affects Versions: 2.0.0
> Reporter: Tim McConnell
> Assignee: Tim McConnell
> Fix For: 2.0.0
>
> Attachments: OPENJPA-1237-2.patch
>
>
> It seems like there should be exception(s) thrown when the new writebehind
> cache is not configured properly. For example, this is not a valid PU
> configuration since there is no DataCache specified.
> <persistence-unit name="WriteBehind_JSE_INVALID_PU1">
> <mapping-file>META-INF/orm.xml</mapping-file>
> <properties>
> <property name="openjpa.DataCache" value="false"/>
>
> <property name="openjpa.WriteBehindCache" value="true"/>
>
> <property name="openjpa.WriteBehindCallback"
> value="true(sleepTime=15000)"/>
> </properties>
> </persistence-unit>
> Yet there is no error or exception thrown when this statement is executed:
> emf =
> Persistence.createEntityManagerFactory("WriteBehind_JSE_INVALID_PU1");
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
