[ https://issues.jboss.org/browse/AS7-5390?page=com.atlassian.jira.plugin.s... ] Heiko Rupp commented on AS7-5390: --------------------------------- [11:36:12] <+pilhuhn> e.g. the above address could have :resolve-path which takes path + relative-to and does the magic [11:38:58] <+jamezp> That looks rather useful. Might be a couple steps to resolve, but seems fairly simple. [11:40:01] <+bstansberry> pilhuhn: if you are looking for a runtime attribute on all the resources that use "path" and "relative-to" that will provide the resolved path, please file a JIRA [11:40:59] <+bstansberry> pilhuhn: that's a smaller scope than a completely generic resolution thing -- 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-5390?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-5390: ---------------------------------- Component/s: Domain Management -- 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-5390?page=com.atlassian.jira.plugin.s... ] James Perkins commented on AS7-5390: ------------------------------------ The transaction subsystem has two relative-to paths. There seems to be two options for dealing with this; # Create an additional operations: {{:resolve-object-store-path}} # Add parameters to the operation to define the the attributes to resolve: {{:resolve-path(relative-to-attribute="object-store-relative-to",path-attribute="object-store-path")}} Transaction Subsystem Model: {code} { "outcome" => "success", "result" => { "default-timeout" => 300, "enable-statistics" => false, "enable-tsm-status" => false, "jts" => false, "node-identifier" => "1", "object-store-path" => "tx-object-store", "object-store-relative-to" => "jboss.server.data.dir", "path" => "var", "process-id-socket-max-ports" => 10, "process-id-uuid" => true, "recovery-listener" => false, "relative-to" => "jboss.server.data.dir", "socket-binding" => "txn-recovery-environment", "status-socket-binding" => "txn-status-manager", "use-hornetq-store" => false, "log-store" => {"log-store" => undefined} } } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-5390?page=com.atlassian.jira.plugin.s... ] James Perkins commented on AS7-5390: ------------------------------------ The more thought I put into this the more it seems a separate operation name is better. Having the management client or user about the model doesn't seem right. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-5390?page=com.atlassian.jira.plugin.s... ] James Perkins commented on AS7-5390: ------------------------------------ Went with the approach of a separate operation for the transaction subsystem. The transaction subsystem has both a {{resolve-path}} and {{resolve-object-store-path}} operation. {code} /subsystem=transactions:resolve-path {code} {code} /subsystem=transactions:resolve-object-store-path {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira