[jboss-jira] [JBoss JIRA] Updated: (JBAS-8135) By default use a common identifier anywhere a server "id" notion is exposed in the configuration
Jason Greene (JIRA)
jira-events at lists.jboss.org
Sun Oct 31 11:43:54 EDT 2010
[ https://jira.jboss.org/browse/JBAS-8135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Greene updated JBAS-8135:
-------------------------------
Fix Version/s: 7.0.0.Beta1
(was: 7.0.0.Alpha1)
> By default use a common identifier anywhere a server "id" notion is exposed in the configuration
> ------------------------------------------------------------------------------------------------
>
> Key: JBAS-8135
> URL: https://jira.jboss.org/browse/JBAS-8135
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 7.0.0.Beta1
>
>
> This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010:
> >> * JBoss Transactions, jvm-route, jboss messaging all require a
> >> unique identifier for them to behave properly in a clustered
> >> environment. I would like one unique identifier for each server
> >> configuration and for all services that need a unique identifier
> >> to reference it by default. Then I don't have to worry about
> >> unique identifiers when creating new servers.
> (The jboss messaging bit is out of date with respect to AS 7, which will use HornetQ and thus has no ServerPeerId configuration required. But the basic point is spot-on.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list