[jboss-jira] [JBoss JIRA] (AS7-1467) Socketbinding :write-attribute(name=includes, value=[]) fails with "no attribute named includes", but :read-resource shows it

Brian Stansberry (Updated) (JIRA) jira-events at lists.jboss.org
Thu Nov 3 16:16:46 EDT 2011


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

Brian Stansberry updated AS7-1467:
----------------------------------

    Fix Version/s: 7.1.0.CR1
      Description: 

[domain at localhost:9999 socket-binding-group=standard-sockets] :read-resource
{
    "outcome" => "success",
    "result" => {
        "default-interface" => "public",
        "includes" => [],
        "name" => "standard-sockets",
        "socket-binding" => {
            "jmx-connector-registry" => undefined,
        }
    }
}
[domain at localhost:9999 socket-binding-group=standard-sockets] :write-attribute(name=includes,value=lala)
{
    "outcome" => "failed",
    "failure-description" => {"domain-failure-description" => "Wrong type for includes. Expected [LIST] but was STRING"},
    "rolled-back" => true
}
[domain at localhost:9999 socket-binding-group=standard-sockets] :write-attribute(name=includes,value=[])  
{
    "outcome" => "failed",
    "result" => {"server-groups" => [("main-server-group" => {"master" => {
    "host" => "master",
    "response" => {
        "outcome" => "failed",
        "failure-description" => "No known attribute called includes",
        "rolled-back" => true
    }
}})]},
    "failure-description" => "Operation failed or was rolled back on all servers.",
    "rolled-back" => true
}
[domain at localhost:9999 socket-binding-group=standard-sockets] :read-children-types
{
    "outcome" => "success",
    "result" => ["socket-binding"]
}
[domain at localhost:9999 socket-binding-group=standard-sockets] 

Also read-attribute works:

[domain at localhost:9999 socket-binding-group=standard-sockets] :read-attribute(name=includes)
{
    "outcome" => "success",
    "result" => []
}

  was:


[domain at localhost:9999 socket-binding-group=standard-sockets] :read-resource
{
    "outcome" => "success",
    "result" => {
        "default-interface" => "public",
        "includes" => [],
        "name" => "standard-sockets",
        "socket-binding" => {
            "jmx-connector-registry" => undefined,
        }
    }
}
[domain at localhost:9999 socket-binding-group=standard-sockets] :write-attribute(name=includes,value=lala)
{
    "outcome" => "failed",
    "failure-description" => {"domain-failure-description" => "Wrong type for includes. Expected [LIST] but was STRING"},
    "rolled-back" => true
}
[domain at localhost:9999 socket-binding-group=standard-sockets] :write-attribute(name=includes,value=[])  
{
    "outcome" => "failed",
    "result" => {"server-groups" => [("main-server-group" => {"master" => {
    "host" => "master",
    "response" => {
        "outcome" => "failed",
        "failure-description" => "No known attribute called includes",
        "rolled-back" => true
    }
}})]},
    "failure-description" => "Operation failed or was rolled back on all servers.",
    "rolled-back" => true
}
[domain at localhost:9999 socket-binding-group=standard-sockets] :read-children-types
{
    "outcome" => "success",
    "result" => ["socket-binding"]
}
[domain at localhost:9999 socket-binding-group=standard-sockets] 

Also read-attribute works:

[domain at localhost:9999 socket-binding-group=standard-sockets] :read-attribute(name=includes)
{
    "outcome" => "success",
    "result" => []
}



We are going to get rid of <include> support in 7.1.
                
> Socketbinding :write-attribute(name=includes,value=[]) fails with "no attribute named includes", but :read-resource shows it
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AS7-1467
>                 URL: https://issues.jboss.org/browse/AS7-1467
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Domain Management
>    Affects Versions: 7.0.0.Final
>            Reporter: Heiko Rupp
>            Assignee: Brian Stansberry
>             Fix For: 7.1.0.CR1
>
>
> [domain at localhost:9999 socket-binding-group=standard-sockets] :read-resource
> {
>     "outcome" => "success",
>     "result" => {
>         "default-interface" => "public",
>         "includes" => [],
>         "name" => "standard-sockets",
>         "socket-binding" => {
>             "jmx-connector-registry" => undefined,
>         }
>     }
> }
> [domain at localhost:9999 socket-binding-group=standard-sockets] :write-attribute(name=includes,value=lala)
> {
>     "outcome" => "failed",
>     "failure-description" => {"domain-failure-description" => "Wrong type for includes. Expected [LIST] but was STRING"},
>     "rolled-back" => true
> }
> [domain at localhost:9999 socket-binding-group=standard-sockets] :write-attribute(name=includes,value=[])  
> {
>     "outcome" => "failed",
>     "result" => {"server-groups" => [("main-server-group" => {"master" => {
>     "host" => "master",
>     "response" => {
>         "outcome" => "failed",
>         "failure-description" => "No known attribute called includes",
>         "rolled-back" => true
>     }
> }})]},
>     "failure-description" => "Operation failed or was rolled back on all servers.",
>     "rolled-back" => true
> }
> [domain at localhost:9999 socket-binding-group=standard-sockets] :read-children-types
> {
>     "outcome" => "success",
>     "result" => ["socket-binding"]
> }
> [domain at localhost:9999 socket-binding-group=standard-sockets] 
> Also read-attribute works:
> [domain at localhost:9999 socket-binding-group=standard-sockets] :read-attribute(name=includes)
> {
>     "outcome" => "success",
>     "result" => []
> }

--
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

        


More information about the jboss-jira mailing list