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

[Martin Simka (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-8960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Simka updated WFLY-8960:
-------------------------------
        Parent:     (was: WFLY-8849)
    Issue Type: Bug  (was: Sub-task)


> CachedConnectionManager custom operations are read-only
> -------------------------------------------------------
>
>                 Key: WFLY-8960
>                 URL: https://issues.jboss.org/browse/WFLY-8960
>             Project: WildFly
>          Issue Type: Bug
>          Components: JCA
>            Reporter: Martin Simka
>            Assignee: Brian Stansberry
>
> *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} 



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)