Application Server 7
  1. Application Server 7
  2. AS7-4073

can not :write-attribute expression values

    Details

    • Similar Issues:
      Show 10 results 

      Description

      socket bindings return on read expression in the form {"EXPRESSION_VALUE":"$

      {foo:123}

      "}

      [standalone@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@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@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},

        Activity

        Hide
        Brian Stansberry
        added a comment -

        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.

        Show
        Brian Stansberry
        added a comment - 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.

          People

          • Assignee:
            Emanuel Muckenhuber
            Reporter:
            Heiko Rupp
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: