[
http://jira.jboss.com/jira/browse/JBCLUSTER-135?page=all ]
Brian Stansberry updated JBCLUSTER-135:
---------------------------------------
Fix Version/s: Q4Y7
(was: Q4Y6)
Affects: [Documentation (Ref Guide, User Guide, etc.),
Compatibility/Configuration] (was: [Compatibility/Configuration, Documentation (Ref
Guide, User Guide, etc.)])
Reducing priority on externalizing cluster project until AS 5 is out, unless there is a
need related to AS 5.
Extract the common use clustering code from the JBoss AS codebase
-----------------------------------------------------------------
Key: JBCLUSTER-135
URL:
http://jira.jboss.com/jira/browse/JBCLUSTER-135
Project: JBoss Clustering
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Priority: Critical
Fix For: Q4Y7
Remoting, Messaging, JBoss Cache and JBoss AS all have clustering aspects to their
functionality. There is potential for code reuse between these projects that can't be
realized if the clustering code resides in the cluster module of the AS codebase.
1) Extract general purpose clustering code from the AS cluster module into a separate
project and produce binaries that other projects can use without creating a dependence on
the AS project.
2) Provide APIs that both support standalone functionality of non-AS projects and
facilitate ease of integration into the AS.
This task is meant to be an umbrella task, with specific detailed subtasks.
This task is primarily focused on meeting the short requirements of JBMESSAGING-516, but
we also need to give due consideration to potential use in other projects.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira