[jboss-jira] [JBoss JIRA] (WFLY-3729) config-properties should be "read-write" by CLI

[Tomaz Cerar (JIRA)]

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

Tomaz Cerar moved JBJCA-1207 to WFLY-3729:
------------------------------------------

              Project: WildFly  (was: IronJacamar)
                  Key: WFLY-3729  (was: JBJCA-1207)
           Issue Type: Enhancement  (was: Bug)
             Workflow: GIT Pull Request workflow   (was: classic default workflow)
    Affects Version/s:     (was: 1.0.17.Final)
          Component/s: JCA
                           (was: AS)


> config-properties should be "read-write" by CLI
> -----------------------------------------------
>
>                 Key: WFLY-3729
>                 URL: https://issues.jboss.org/browse/WFLY-3729
>             Project: WildFly
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: JCA
>         Environment: EAP 6.1.0
> RHEL 6.5
>            Reporter: Jooho Lee
>            Assignee: Jesper Pedersen
>              Labels: eap6, jboss
>
> Using CLI, it is possible to control websphere message server but config-properties can not be modified or created because its access-type is read-only.
> For example,
> {code:title=CLI Command|borderStyle=solid}
> /profile=MMPS-dev-03-profile/subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/admin-objects=FDSLPublishQueue/config-properties=baseQueueName:write-attribute(name=value,value=test)
> {
>     "outcome" => "failed",
>     "failure-description" => "JBAS014639: Attribute value is not writable",
>     "rolled-back" => true
> }
> {code}
> This is because the fact that baseQueueName(config-properties)' access-type is read-only but I don't see any reasons why this attritbute couldn't be writable.
> Is there any reasons the attribute has to be read-only? otherwise, it should be read-write.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)