[jboss-jira] [JBoss JIRA] (AS7-348) By default use a common identifier anywhere a server "id" notion is exposed in the configuration
Jason Greene (Updated) (JIRA)
jira-events at lists.jboss.org
Fri Nov 4 14:10:58 EDT 2011
[ https://issues.jboss.org/browse/AS7-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Greene updated AS7-348:
-----------------------------
Moving all non-critical issues to the CR. If you finish it before we release beta please correct the fix-for version.
Thanks
> By default use a common identifier anywhere a server "id" notion is exposed in the configuration
> ------------------------------------------------------------------------------------------------
>
> Key: AS7-348
> URL: https://issues.jboss.org/browse/AS7-348
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: David Lloyd
> Fix For: 7.1.0.CR1
>
>
> 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, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list