[
https://issues.apache.org/jira/browse/JS2-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Sean Taylor updated JS2-893:
----------------------------------
Fix Version/s: (was: 2.1.3)
(was: 2.1.2)
I am changing the fix version to 2.2, since I cannot modify the database tables
to a post release.
Will review this before the 2.2 release and make a decision whether it should
be included in the release as an optional or default feature.
> cluster synchronization feature
> -------------------------------
>
> Key: JS2-893
> URL: https://issues.apache.org/jira/browse/JS2-893
> Project: Jetspeed 2
> Issue Type: New Feature
> Components: Other
> Affects Versions: 2.1.2, 2.1.3, 2.2
> Reporter: Joachim Müller
> Assignee: David Sean Taylor
> Fix For: 2.2
>
> Attachments: JS2-893_patch.zip
>
>
> We developed a cluster synchronization feature that is able to synchronize
> the execution of an objects method cluster-wide. The approach is similar to
> the spring transaction proxy, so we are able to AOP-inject the cluster
> synchronization via spring configuration. The component is highly
> customizable. A new database table is used for synchonization, but any other
> data container (i.e. broadcast-distributed-hashmap) could be used.
> One main application for this functionality is the start of many jetspeed
> cluster nodes and synchronize the deployment of the PAs to the database.
> (Even with the VersionedApplicationManager we experienced DB constraints
> failures on startup with fresh database, preventing the some PAs from
> registration.)
> Patch follows (exists only for the 2.1.2-POSTRELEASE branch yet).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
