[jboss-jira] [JBoss JIRA] (WFLY-8853) CachedConnectionManager custom operations are read-only

[ https://issues.jboss.org/browse/WFLY-8853?page=com.atlassian.jira.plugin.... ] Martin Simka updated WFLY-8853: ------------------------------- Description: *CRITICAL: DO NOT IMPLEMENT THIS IF WFCORE-2858 IS NOT IN PLACE.* Otherwise existing behavior will regress. Subtask for the following item from the parent issue: {quote} JcaCachedConnectionManagerDefinition.CcmOperations has two operations that are not declared to be read-only that are registered on the profile resource. So these are pre-existing ops that break the no-runtime-only-on-profile rule that WFCORE-389 is about rescinding. A twist with these is they seem to actually be read-only and should be described as such. But if we do that we must implement WFCORE-2858 to avoid breaking existing behavior. {quote} was: *CRITICAL: DO NOT IMPLEMENT THIS IF WFCORE-2828 IS NOT IN PLACE.* Otherwise existing behavior will regress. Subtask for the following item from the parent issue: {quote} JcaCachedConnectionManagerDefinition.CcmOperations has two operations that are not declared to be read-only that are registered on the profile resource. So these are pre-existing ops that break the no-runtime-only-on-profile rule that WFCORE-389 is about rescinding. A twist with these is they seem to actually be read-only and should be described as such. But if we do that we must implement WFCORE-2858 to avoid breaking existing behavior. {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)