[ https://issues.jboss.org/browse/AS7-2792?page=com.atlassian.jira.plugin.s... ] Alexey Loubyansky reassigned AS7-2792: -------------------------------------- Assignee: Brian Stansberry (was: Alexey Loubyansky) This also belongs the domain management. Property resolution (if has to be done) has to happen on the server side. -- 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

[ https://issues.jboss.org/browse/AS7-2792?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-2792: ---------------------------------- Fix Version/s: Open To Community (was: 7.2.0.Alpha1) -- 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

[ https://issues.jboss.org/browse/AS7-2792?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz commented on AS7-2792: ------------------------------------------ Rosta This question is best placed for Brian, but i'll present my understanding of it as it applies to the JGroups subsystem. If I understand correctly, this issue is not particular to socket-binding definitions, but to any model attribute whose value is an expression. When an attribute whose value is an expression is viewed from the management interface, the unresolved expression is displayed, not the resolved value, as it reflects the value of the attribute in the persistent model, and the persistent model needs to be server-instance neutral. Such expressions are resolved when services are started in a particular server context, but those resolved values are generally not available for viewing. The option include-runtime does not cause the resolved value of the attribute to be displayed, but rather displays attributes which are defined as runtime attributes (i.e. are not part of the persistent configuration, which is server instance neutral) - not the same thing. It would be possible to define a runtime attribute which read and made observable the resolved multicast address, but that would be one particular solution to a more general problem. I expect that you would like to have an option where you may connect to a server and see the model with all expressions resolved in the context of that server's environment; like: {noformat} :read-resource(resolve-expressions=true) {noformat} so that the resolved model can be viewed. Is that correct? -- 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

[ https://issues.jboss.org/browse/AS7-2792?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-2792: --------------------------------------- You can use the root-resource's "resolve-expression" operation to resolve any expression: cd / :resolve-expression(expression=${jboss.default.multicast.address:230.0.0.4}) -- 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