[
https://issues.jboss.org/browse/AS7-4537?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-4537:
---------------------------------------
I've pinged some relevant stakeholders re: whether we can remove the legacy configs.
They are there for backwards compatibility reasons.
Jason and I agree though that there is no need to support these legacy configs in the
console. I think a tool tip or something explaining why the socket-binding info isn't
displayed would be nice, but I see no need to display all the legacy config details in the
console.
Messaging management layer exposes redundant information
--------------------------------------------------------
Key: AS7-4537
URL:
https://issues.jboss.org/browse/AS7-4537
Project: Application Server 7
Issue Type: Enhancement
Components: Domain Management, JMS
Reporter: Heiko Braun
Assignee: Jeff Mesnil
Fix For: 7.1.2.Final-redhat1
Take a look at
{noformat}
/subsystem=messaging/hornetq-server=default/broadcast-group=*:read-resource-description
{noformat}
it exposes redundant configuration options that overlap with the socket binding and
interface concepts.
IMO these will need to be removed from the messaging subsystem management exposure so
that it solely relies on socket binding and interface references instead.
--
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