[jboss-as7-dev] Result "undefined"?

[Brian Stansberry]

It's analogous to the void return value of standard property setters or 
MBeanServer.setAttribute. The contract of the operation is if it returns 
successfully the attribute now has the provided value.

I'm leery of changing it as it imposes a burden on the OperationHandler 
impls for all writable attributes to pass back the new value. They 
mostly inherit from a common superclass where I could add that, so if 
it's important I can consider it. But it introduces a subtle source of 
bugs if clients were to depend on the value.

On 4/12/11 1:55 PM, Heiko W.Rupp wrote:
> Hi,
>
> [localhost:9999 /host=pintsize/server-config=server-four] :write-attribute(name=auto-start,value=false)
> {
>      "outcome" =>  "success",
>      "result" =>  undefined,
>
> Why is the result "undefined"? Shouldn't that  be the value that has been written ?
>
>      "compensating-operation" =>  {
>          "operation" =>  "write-attribute",
>          "address" =>  [
>              ("host" =>  "pintsize"),
>              ("server-config" =>  "server-four")
>          ],
>          "name" =>  "auto-start",
>          "value" =>  true
>      }
>


-- 
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat