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 Fix For: 7.0.0.M1 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.)

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.)

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 Fix For: 7.1.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.)

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.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.)

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.)

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.)

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: Paul Ferraro Fix For: 7.1.0.Final 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.)