[ https://issues.jboss.org/browse/AS7-4431?page=com.atlassian.jira.plugin.s... ] Simeon Pinder updated AS7-4431: ------------------------------- Description: The address for 'subsystem=mail/mail-session=java:jboss/mail/Default' must be escaped because of the ':' and '/' characters in the 'mail-session' node. Log in via the DMR cli shell and you're able to browse the same node via '/subsystem=mail/mail-session=java\:jboss\/mail\/Default/:read-resource' If you attempt to read the same node via escaped json you get: failureDescription=JBAS014807: Management resource '[ ("subsystem" => "mail"), ("mail-session" => "java\\:jboss\\/mail\\/Default") ]' not found, rolledBack=true} was: The address for 'subsystem=mail/mail-session=java:jboss/mail/Default' must be escaped because of the ':' and '/' characters in the 'mail-session' node. Log in via the DMR cli shell and you're able to browse the same node via '/subsystem=mail/mail-session=java\:jboss\/mail\/Default/:read-resource' If you attempt to read the same node via escaped json you get: failureDescription=JBAS014807: Management resource '[ ("subsystem" => "mail"), ("mail-session" => "java\\\\:jboss\\\\/mail\\\\/Default") ]' not found, rolledBack=true} -- 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-4431?page=com.atlassian.jira.plugin.s... ] Simeon Pinder commented on AS7-4431: ------------------------------------ No. I should have been more explicit. Browsing the posted path(subsystem=mail/mail-session=java:jboss/mail/Default) via native cli worked as expected and automatically generated the escaping of ':' and '/' correctly. Our json client had issues communicating with 'subsystem=mail/mail-session=java:jboss/mail/Default' and I assumed that we needed to add the same escaping for that address to work. After adding the escape code I still encountered communication errors for that node and assumed a JIRA needed to be filed. Since this time we have determined that this JIRA is invalid. We've traced the error back to issues in our json client code that have since been rectified. Essentially by trying to support both native cli addresses and our own client side(json) addressing we had a subtle error of double escaping that was occurring and give rise to this JIRA. Please close this issue. -- 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