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

Jooho Lee (JIRA) issues at jboss.org
Tue Aug 12 19:18:29 EDT 2014


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

Jooho Lee updated JBJCA-1207:
-----------------------------

    Summary: config-properties should be "read-write" by CLI  (was: config-properties should be "read-writable" by CLI)


> config-properties should be "read-write" by CLI
> -----------------------------------------------
>
>                 Key: JBJCA-1207
>                 URL: https://issues.jboss.org/browse/JBJCA-1207
>             Project: IronJacamar
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: AS
>    Affects Versions: 1.0.17.Final
>         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)


More information about the jboss-jira mailing list