[ https://issues.jboss.org/browse/AS7-4084?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated AS7-4084: ---------------------------------- Fix Version/s: 7.2.0.Alpha1 (was: 7.1.2.Final (EAP)) 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-4084?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz commented on AS7-4084: ------------------------------------------ Implemented the code that Tristan provided into the Infinispan subsystem recently refactored into resources. Encountered the following problem: <quote> Infinispan and JGroups gather statistics in certain associated services (e.g. TransactionManager, RpcManager,...). These services are installed at boot time, but not started until someone deploys a clustering application which uses them. So, if I try to read one of their read-only attributes before a deployment has occurred, I throw an OperationFailedException with a message saying that the required service has not been started. This works fine and seems to be the right way to proceed. On the other hand, there is a smoke test case BasicOperationsUnitTestCase.testRecursiveReadIncludingRuntime() which seems to assume that all reads of runtime-only resources will succeed. </quote> Is it really the case that every read of a read-only attribute should always succeed? If so, what is the best way to work around this? Can I somehow return an informational message instead of throwing an exception? Checking these issues with Emanuel M. -- 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-4084?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz commented on AS7-4084: ------------------------------------------ In that case, you seem to be activating whole child resources by conditionally returning resources in response to getChild() calls. In what we had set up so far, we need to turn on a subset of attributes for a specific resource; e.g. /susbsystem=infinispan/cache-container=X // always available attributes A B C // attributes available when a particular MSC service is running D E Can the method used in the Messaging case also be used to cater to the above? In other words, what mechanism can be used to "turn-on" and "turn-off" the visibility of the attributes, as opposed to children? -- 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-4084?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz commented on AS7-4084: ------------------------------------------ Brian, I have followed your recommendations on dealing with exceptional conditions in handlers. I also log a WARN message just for the record so that the differing causes of undefined values can be determined. -- 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