[
https://issues.apache.org/jira/browse/OPENJPA-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12897465#action_12897465
]
Jeremy Bauer commented on OPENJPA-1763:
---------------------------------------
+1 While this requirement makes it very clear that the cache can be
distributed, it complicates configuration for the simple and probably most
common case. If this can be done without breaking product derivations and
such, I think we should do it.
> Remove the requirement to configure openjpa.RemoteCommitProvider when using
> the DataCache
> -----------------------------------------------------------------------------------------
>
> Key: OPENJPA-1763
> URL: https://issues.apache.org/jira/browse/OPENJPA-1763
> Project: OpenJPA
> Issue Type: Improvement
> Components: datacache
> Affects Versions: 2.1.0
> Reporter: Rick Curtis
> Assignee: Rick Curtis
> Fix For: 2.1.0
>
>
> I've been annoyed for quite some time that when I want to use the DataCache I
> need to configure it in two steps. One to turn on the DataCache(obviously),
> and the second is to enable a RemoteCommitProvider.
> <property name="openjpa.DataCache" value="true(CacheSize=10000)"/>
> <property name="openjpa.RemoteCommitProvider" value="sjvm" />
> With this JIRA I'm proposing that when the DataCache is enabled we auto
> configure the sjvm RCP if there isn't one already there.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
