[jboss-jira] [JBoss JIRA] (WFCORE-4923) wildfly should resolve expression recursively

[Tamás Ábele (Jira)]

     [ https://issues.redhat.com/browse/WFCORE-4923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tamás Ábele updated WFCORE-4923:
--------------------------------
    Description: 
The problem affects all versions. The wildfly controller does not resolve expression resursively which causes improper behaviour of the jbos CLI. 

{code:json}
[standalone at localhost:9992 /] /subsystem=batch-jberet:read-resource(include-runtime=true,recursive=true,resolve-expressions=true)
{
    "outcome" => "success",
    "result" => {
        "restart-jobs-on-resume" => true,
        "security-domain" => undefined,
        "default-job-repository" => "in-memory",
        "default-thread-pool" => "batch",
        "in-memory-job-repository" => {"in-memory" => {}},
        "jdbc-job-repository" => undefined,
        "thread-factory" => undefined,
        "thread-pool" => {"batch" => {
            "active-count" => 0,
            "completed-task-count" => 0L,
            "current-thread-count" => 0,
            "keepalive-time" => {
                "time" => 30L,
                "unit" => "SECONDS"
            },
            "largest-thread-count" => 0,
            "max-threads" => expression "${batch-max-threads}",
            "name" => "batch",
            "queue-size" => 0,
            "rejected-count" => 0,
            "task-count" => 0L,
            "thread-factory" => undefined
        }}
    }
}

{code}


The missing recursive expression resolvation also causes runtime errors in the wildfly console (HAL) if you use properties your configuration XML-s (standalone.xml, domain.xml, ...) Two examples can be found in the attachements. 




  was:
The problem affects all versions. The wildfly controller does not resolve expression resursively which causes improper behaviour of the jbos CLI. 

{code:json}
[standalone at localhost:9992 /] /subsystem=batch-jberet:read-resource(include-runtime=true,recursive=true,resolve-expressions=true)
{
    "outcome" => "success",
    "result" => {
        "restart-jobs-on-resume" => true,
        "security-domain" => undefined,
        "default-job-repository" => "in-memory",
        "default-thread-pool" => "batch",
        "in-memory-job-repository" => {"in-memory" => {}},
        "jdbc-job-repository" => undefined,
        "thread-factory" => undefined,
        "thread-pool" => {"batch" => {
            "active-count" => 0,
            "completed-task-count" => 0L,
            "current-thread-count" => 0,
            "keepalive-time" => {
                "time" => 30L,
                "unit" => "SECONDS"
            },
            "largest-thread-count" => 0,
            "max-threads" => expression "${batch-max-threads}",
            "name" => "batch",
            "queue-size" => 0,
            "rejected-count" => 0,
            "task-count" => 0L,
            "thread-factory" => undefined
        }}
    }
}

{code}


The missing recursive expression resolvation also causes runtime errors in the wildfly console (HAL) if you use properties your configuration XML-s (standalone.xml, domain.xml, ...)






> wildfly should resolve expression recursively
> ---------------------------------------------
>
>                 Key: WFCORE-4923
>                 URL: https://issues.redhat.com/browse/WFCORE-4923
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: Server
>            Reporter: Tamás Ábele
>            Assignee: Jeff Mesnil
>            Priority: Major
>         Attachments: hal-error1.png, hal-error2.png
>
>
> The problem affects all versions. The wildfly controller does not resolve expression resursively which causes improper behaviour of the jbos CLI. 
> {code:json}
> [standalone at localhost:9992 /] /subsystem=batch-jberet:read-resource(include-runtime=true,recursive=true,resolve-expressions=true)
> {
>     "outcome" => "success",
>     "result" => {
>         "restart-jobs-on-resume" => true,
>         "security-domain" => undefined,
>         "default-job-repository" => "in-memory",
>         "default-thread-pool" => "batch",
>         "in-memory-job-repository" => {"in-memory" => {}},
>         "jdbc-job-repository" => undefined,
>         "thread-factory" => undefined,
>         "thread-pool" => {"batch" => {
>             "active-count" => 0,
>             "completed-task-count" => 0L,
>             "current-thread-count" => 0,
>             "keepalive-time" => {
>                 "time" => 30L,
>                 "unit" => "SECONDS"
>             },
>             "largest-thread-count" => 0,
>             "max-threads" => expression "${batch-max-threads}",
>             "name" => "batch",
>             "queue-size" => 0,
>             "rejected-count" => 0,
>             "task-count" => 0L,
>             "thread-factory" => undefined
>         }}
>     }
> }
> {code}
> The missing recursive expression resolvation also causes runtime errors in the wildfly console (HAL) if you use properties your configuration XML-s (standalone.xml, domain.xml, ...) Two examples can be found in the attachements. 



--
This message was sent by Atlassian Jira
(v7.13.8#713008)