[jboss-jira] [JBoss JIRA] (WFLY-3729) config-properties should be "read-write" by CLI
RH Bugzilla Integration (JIRA)
issues at jboss.org
Tue Sep 2 15:48:59 EDT 2014
[ https://issues.jboss.org/browse/WFLY-3729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998092#comment-12998092 ]
RH Bugzilla Integration commented on WFLY-3729:
-----------------------------------------------
Jesper Pedersen <jpederse at redhat.com> changed the Status of [bug 1129496|https://bugzilla.redhat.com/show_bug.cgi?id=1129496] from NEW to CLOSED
> 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.3.1#6329)
More information about the jboss-jira
mailing list