[jboss-jira] [JBoss JIRA] (AS7-4073) can not :write-attribute expression values

[Brian Stansberry (JIRA)]

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

Brian Stansberry updated AS7-4073:
----------------------------------

    Fix Version/s: 7.1.1.Final
         Priority: Critical  (was: Major)


Diagnosis: AbstractBindingWriteHandler wasn't converted to use the AttributeDefintitions declared in AbstractSocketBindingResourceDefinition. A similar issue may exist for InterfaceCriteriaWriteHandler. See the AttributeDefinition logic in validateOperation() -- that needs to be applied.
                
> can not :write-attribute expression values
> ------------------------------------------
>
>                 Key: AS7-4073
>                 URL: https://issues.jboss.org/browse/AS7-4073
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 7.1.0.Final
>            Reporter: Heiko Rupp
>            Assignee: Brian Stansberry
>            Priority: Critical
>              Labels: rhq
>             Fix For: 7.1.1.Final
>
>
> socket bindings return on read expression in the form {"EXPRESSION_VALUE":"${foo:123}"}
> [standalone at localhost:9999 socket-binding=management-http] :read-attribute(name=port)          
> {
>     "outcome" => "success",
>     "result" => expression "${jboss.management.http.port:9990}"
> }
> First this is confusing, as the description describes the port as int:
> [standalone at localhost:9999 socket-binding=http] :read-resource-description
> {
>     "outcome" => "success",
>     "result" => {
>         "description" => "Configuration information for a socket.",
>         "attributes" => {
>             "port" => {
>                 "type" => INT,
>                 "description" => "Number of the port to which the socket should be bound.",
>                 "expressions-allowed" => true,
>                 "nillable" => false,
>                 "min" => 0L,
>                 "max" => 65535L,
>                 "access-type" => "read-write",
>                 "storage" => "configuration",
>                 "restart-required" => "all-services"
>             },
> I can still work around this in json-land by having the expression toString()'d and then remove the {EXPRESSION_VALUE=..} part around it.
> Now writing back an expression does not work:
> [standalone at localhost:9999 socket-binding=management-http] :write-attribute(name=port,value=${jboss.management.http.port:19990})
> {
>     "outcome" => "failed",
>     "failure-description" => "JBAS014688: Wrong type for port. Expected [EXPRESSION, INT] but was STRING",
>     "rolled-back" => true
> }
> Same applies to json-interface when I do a write-attribute call with  {name="port",value="${...}"}   as payload
>  Operation <CompositeOperation{steps=23}> returned <"JBAS014688: Wrong type for port. Expected [EXPRESSION, INT] but was STRING","rolled-back":true},

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira