You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Thomas Mueller (JIRA)" <ji...@apache.org> on 2009/12/09 14:42:18 UTC
[jira] Created: (JCR-2429) Clustering is broken due to duplicated
CachingPersistenceManager interface
Clustering is broken due to duplicated CachingPersistenceManager interface
--------------------------------------------------------------------------
Key: JCR-2429
URL: https://issues.apache.org/jira/browse/JCR-2429
Project: Jackrabbit Content Repository
Issue Type: Bug
Components: clustering, jackrabbit-core
Affects Versions: 2.0-beta3
Reporter: Thomas Mueller
Assignee: Thomas Mueller
There are now two interfaces CachingPersistenceManager in the packages org.apache.jackrabbit.core.persistence.bundle and org.apache.jackrabbit.core.persistence.pool. A persistence manager that implements the ..bundle... interface doesn't receive the onExternalUpdate events that are required for clustering to work.
I will move this interface to the package org.apache.jackrabbit.core.persistence and remove the second implementation.
This change has no affect to backward compatibility, because anyway there were many breaking changes in the past (NodeId / UUID for example).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-2429) Clustering is broken due to duplicated
CachingPersistenceManager interface
Posted by "Thomas Mueller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Mueller resolved JCR-2429.
---------------------------------
Resolution: Fixed
> Clustering is broken due to duplicated CachingPersistenceManager interface
> --------------------------------------------------------------------------
>
> Key: JCR-2429
> URL: https://issues.apache.org/jira/browse/JCR-2429
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: clustering, jackrabbit-core
> Affects Versions: 2.0-beta4
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Fix For: 2.0.0
>
>
> There are now two interfaces CachingPersistenceManager in the packages org.apache.jackrabbit.core.persistence.bundle and org.apache.jackrabbit.core.persistence.pool. A persistence manager that implements the ..bundle... interface doesn't receive the onExternalUpdate events that are required for clustering to work.
> I will move this interface to the package org.apache.jackrabbit.core.persistence and remove the second implementation.
> This change has no affect to backward compatibility, because anyway there were many breaking changes in the past (NodeId / UUID for example).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-2429) Clustering is broken due to duplicated
CachingPersistenceManager interface
Posted by "Thomas Mueller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Mueller updated JCR-2429:
--------------------------------
Affects Version/s: (was: 2.0-beta3)
2.0-beta4
Fix Version/s: 2.0.0
> Clustering is broken due to duplicated CachingPersistenceManager interface
> --------------------------------------------------------------------------
>
> Key: JCR-2429
> URL: https://issues.apache.org/jira/browse/JCR-2429
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: clustering, jackrabbit-core
> Affects Versions: 2.0-beta4
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Fix For: 2.0.0
>
>
> There are now two interfaces CachingPersistenceManager in the packages org.apache.jackrabbit.core.persistence.bundle and org.apache.jackrabbit.core.persistence.pool. A persistence manager that implements the ..bundle... interface doesn't receive the onExternalUpdate events that are required for clustering to work.
> I will move this interface to the package org.apache.jackrabbit.core.persistence and remove the second implementation.
> This change has no affect to backward compatibility, because anyway there were many breaking changes in the past (NodeId / UUID for example).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JCR-2429) Clustering is broken due to duplicated
CachingPersistenceManager interface
Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788654#action_12788654 ]
Jukka Zitting commented on JCR-2429:
------------------------------------
+1 There are probably a few other duplicate bundle/pool classes that don't really need to be duplicated.
> Clustering is broken due to duplicated CachingPersistenceManager interface
> --------------------------------------------------------------------------
>
> Key: JCR-2429
> URL: https://issues.apache.org/jira/browse/JCR-2429
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: clustering, jackrabbit-core
> Affects Versions: 2.0-beta4
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Fix For: 2.0.0
>
>
> There are now two interfaces CachingPersistenceManager in the packages org.apache.jackrabbit.core.persistence.bundle and org.apache.jackrabbit.core.persistence.pool. A persistence manager that implements the ..bundle... interface doesn't receive the onExternalUpdate events that are required for clustering to work.
> I will move this interface to the package org.apache.jackrabbit.core.persistence and remove the second implementation.
> This change has no affect to backward compatibility, because anyway there were many breaking changes in the past (NodeId / UUID for example).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.