[JBoss JIRA] (WFCORE-4923) read-resource operation does not resolve expressions recursively
by Tamás Ábele (Jira)
[ https://issues.redhat.com/browse/WFCORE-4923?page=com.atlassian.jira.plug... ]
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@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.
The solution would be only adding the
{code:java}
rrOp.get(ModelDescriptionConstants.RESOLVE_EXPRESSIONS).set(resolve);
{code}
line after
{code:java}
rrOp.get(ModelDescriptionConstants.INCLUDE_DEFAULTS).set(defaults);
{code}
in the doExecuteInternal method of the
\controller\src\main\java\org\jboss\as\controller\operations\global\ReadResourceHandler.java
The wildfly console (HAL) source code is also buggy
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@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.
The solution would be only adding the
{code:java}
rrOp.get(ModelDescriptionConstants.RESOLVE_EXPRESSIONS).set(resolve);
{code}
line after
{code:java}
rrOp.get(ModelDescriptionConstants.INCLUDE_DEFAULTS).set(defaults);
{code}
in the doExecuteInternal method of the
\controller\src\main\java\org\jboss\as\controller\operations\global\ReadResourceHandler.java
> read-resource operation does not resolve expressions recursively
> ----------------------------------------------------------------
>
> Key: WFCORE-4923
> URL: https://issues.redhat.com/browse/WFCORE-4923
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Affects Versions: 12.0.0.Beta1
> 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@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.
> The solution would be only adding the
> {code:java}
> rrOp.get(ModelDescriptionConstants.RESOLVE_EXPRESSIONS).set(resolve);
> {code}
> line after
> {code:java}
> rrOp.get(ModelDescriptionConstants.INCLUDE_DEFAULTS).set(defaults);
> {code}
> in the doExecuteInternal method of the
> \controller\src\main\java\org\jboss\as\controller\operations\global\ReadResourceHandler.java
> The wildfly console (HAL) source code is also buggy
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (WFCORE-4925) Correct GAV versions in ModelTestControllerVersion
by Richard Achmatowicz (Jira)
[ https://issues.redhat.com/browse/WFCORE-4925?page=com.atlassian.jira.plug... ]
Richard Achmatowicz updated WFCORE-4925:
----------------------------------------
Fix Version/s: 12.0.0.Beta2
(was: 11.0.1.Final)
> Correct GAV versions in ModelTestControllerVersion
> --------------------------------------------------
>
> Key: WFCORE-4925
> URL: https://issues.redhat.com/browse/WFCORE-4925
> Project: WildFly Core
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 12.0.0.Beta2
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Priority: Major
> Fix For: 12.0.0.Beta2
>
>
> The class org.jboss.as.model.test.ModelTestControllerVersion is used to provide component versioning information for various versions of EAP and Wildfly.
> Given a version of EAP, say, 7.2.0, this class can be used to find the maven version for the product maven artifact, as well the maven version of Wildfly Core artifact used, etc.
> The maven versions for EAP and Wildfly Core use "productized" versions, incorporating the -redhat- tag (e.g. org.wildfly.core:wildfly-threads:6.0.11.Final-redhat-1)
> Currently, ModelTestControllerVersion uses "productized" version numbers for the EAP maven artifact but not for Wildfly Core maven artifact. This means that this class cannot be used to easily specify the maven version for the Wildfly Core component of the EAP version.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (WFCORE-4925) Correct GAV versions in ModelTestControllerVersion
by Richard Achmatowicz (Jira)
Richard Achmatowicz created WFCORE-4925:
-------------------------------------------
Summary: Correct GAV versions in ModelTestControllerVersion
Key: WFCORE-4925
URL: https://issues.redhat.com/browse/WFCORE-4925
Project: WildFly Core
Issue Type: Bug
Components: Test Suite
Affects Versions: 11.0.0.Final
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 11.0.1.Final
The class org.jboss.as.model.test.ModelTestControllerVersion is used to provide component versioning information for various versions of EAP and Wildfly.
Given a version of EAP, say, 7.2.0, this class can be used to find the maven version for the product maven artifact, as well the maven version of Wildfly Core artifact used, etc.
The maven versions for EAP and Wildfly Core use "productized" versions, incorporating the -redhat- tag (e.g. org.wildfly.core:wildfly-threads:6.0.11.Final-redhat-1)
Currently, ModelTestControllerVersion uses "productized" version numbers for the EAP maven artifact but not for Wildfly Core maven artifact. This means that this class cannot be used to easily specify the maven version for the Wildfly Core component of the EAP version.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (WFCORE-4925) Correct GAV versions in ModelTestControllerVersion
by Richard Achmatowicz (Jira)
[ https://issues.redhat.com/browse/WFCORE-4925?page=com.atlassian.jira.plug... ]
Richard Achmatowicz updated WFCORE-4925:
----------------------------------------
Affects Version/s: 12.0.0.Beta2
(was: 11.0.0.Final)
> Correct GAV versions in ModelTestControllerVersion
> --------------------------------------------------
>
> Key: WFCORE-4925
> URL: https://issues.redhat.com/browse/WFCORE-4925
> Project: WildFly Core
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 12.0.0.Beta2
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Priority: Major
> Fix For: 12.0.0.Beta2
>
>
> The class org.jboss.as.model.test.ModelTestControllerVersion is used to provide component versioning information for various versions of EAP and Wildfly.
> Given a version of EAP, say, 7.2.0, this class can be used to find the maven version for the product maven artifact, as well the maven version of Wildfly Core artifact used, etc.
> The maven versions for EAP and Wildfly Core use "productized" versions, incorporating the -redhat- tag (e.g. org.wildfly.core:wildfly-threads:6.0.11.Final-redhat-1)
> Currently, ModelTestControllerVersion uses "productized" version numbers for the EAP maven artifact but not for Wildfly Core maven artifact. This means that this class cannot be used to easily specify the maven version for the Wildfly Core component of the EAP version.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (DROOLS-4589) Refactor of Scorecards
by Gabriele Cardosi (Jira)
[ https://issues.redhat.com/browse/DROOLS-4589?page=com.atlassian.jira.plug... ]
Gabriele Cardosi updated DROOLS-4589:
-------------------------------------
Description:
_{color:#C1C7D0}(Re-design and refactoring of Scorecard model in kie-pmml module. The result of which should be...
* Scorecard models uses a standardized "pipeline" for processing requests to apply a model to input data
* Scorecard models use the "re-usable alpha network" approach when possible, minimizing the use of KieSessions and rete.
* Scorecard models use a minimal amount of rules when applying the model to input data, and any generated rules should be in executable model form/format
* Scorecard models are -applied- via a service interface old specs){color}_
was:
-Re-design and refactoring of Scorecard model in kie-pmml module. The result of which should be...
* Scorecard models uses a standardized "pipeline" for processing requests to apply a model to input data
* Scorecard models use the "re-usable alpha network" approach when possible, minimizing the use of KieSessions and rete.
* Scorecard models use a minimal amount of rules when applying the model to input data, and any generated rules should be in executable model form/format
* Scorecard models are -applied- via a service interface-
> Refactor of Scorecards
> ----------------------
>
> Key: DROOLS-4589
> URL: https://issues.redhat.com/browse/DROOLS-4589
> Project: Drools
> Issue Type: Task
> Components: PMML
> Reporter: Lance Leverich
> Assignee: Gabriele Cardosi
> Priority: Major
> Labels: CustomerFocusTeam, TrustyAI
>
> _{color:#C1C7D0}(Re-design and refactoring of Scorecard model in kie-pmml module. The result of which should be...
> * Scorecard models uses a standardized "pipeline" for processing requests to apply a model to input data
> * Scorecard models use the "re-usable alpha network" approach when possible, minimizing the use of KieSessions and rete.
> * Scorecard models use a minimal amount of rules when applying the model to input data, and any generated rules should be in executable model form/format
> * Scorecard models are -applied- via a service interface old specs){color}_
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (DROOLS-4589) Refactor of Scorecards
by Gabriele Cardosi (Jira)
[ https://issues.redhat.com/browse/DROOLS-4589?page=com.atlassian.jira.plug... ]
Gabriele Cardosi updated DROOLS-4589:
-------------------------------------
Description:
Re-design and refactoring of Scorecard model in kie-pmml module. The result of which should be...
* Scorecard models uses a standardized "pipeline" for processing requests to apply a model to input data
* Scorecard models use the "re-usable alpha network" approach when possible, minimizing the use of KieSessions and rete.
* Scorecard models use a minimal amount of rules when applying the model to input data, and any generated rules should be in executable model form/format
* Scorecard models are applied via a service interface
was:
--Re-design and refactoring of Scorecard model in kie-pmml module. The result of which should be...
* Scorecard models uses a standardized "pipeline" for processing requests to apply a model to input data
* Scorecard models use the "re-usable alpha network" approach when possible, minimizing the use of KieSessions and rete.
* Scorecard models use a minimal amount of rules when applying the model to input data, and any generated rules should be in executable model form/format
* Scorecard models are applied via a service interface--
> Refactor of Scorecards
> ----------------------
>
> Key: DROOLS-4589
> URL: https://issues.redhat.com/browse/DROOLS-4589
> Project: Drools
> Issue Type: Task
> Components: PMML
> Reporter: Lance Leverich
> Assignee: Gabriele Cardosi
> Priority: Major
> Labels: CustomerFocusTeam, TrustyAI
>
> Re-design and refactoring of Scorecard model in kie-pmml module. The result of which should be...
> * Scorecard models uses a standardized "pipeline" for processing requests to apply a model to input data
> * Scorecard models use the "re-usable alpha network" approach when possible, minimizing the use of KieSessions and rete.
> * Scorecard models use a minimal amount of rules when applying the model to input data, and any generated rules should be in executable model form/format
> * Scorecard models are applied via a service interface
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (DROOLS-4589) Refactor of Scorecards
by Gabriele Cardosi (Jira)
[ https://issues.redhat.com/browse/DROOLS-4589?page=com.atlassian.jira.plug... ]
Gabriele Cardosi updated DROOLS-4589:
-------------------------------------
Description:
-Re-design and refactoring of Scorecard model in kie-pmml module. The result of which should be...
* Scorecard models uses a standardized "pipeline" for processing requests to apply a model to input data
* Scorecard models use the "re-usable alpha network" approach when possible, minimizing the use of KieSessions and rete.
* Scorecard models use a minimal amount of rules when applying the model to input data, and any generated rules should be in executable model form/format
* Scorecard models are applied via a service interface-
was:
Re-design and refactoring of Scorecard model in kie-pmml module. The result of which should be...
* Scorecard models uses a standardized "pipeline" for processing requests to apply a model to input data
* Scorecard models use the "re-usable alpha network" approach when possible, minimizing the use of KieSessions and rete.
* Scorecard models use a minimal amount of rules when applying the model to input data, and any generated rules should be in executable model form/format
* Scorecard models are applied via a service interface
> Refactor of Scorecards
> ----------------------
>
> Key: DROOLS-4589
> URL: https://issues.redhat.com/browse/DROOLS-4589
> Project: Drools
> Issue Type: Task
> Components: PMML
> Reporter: Lance Leverich
> Assignee: Gabriele Cardosi
> Priority: Major
> Labels: CustomerFocusTeam, TrustyAI
>
> -Re-design and refactoring of Scorecard model in kie-pmml module. The result of which should be...
> * Scorecard models uses a standardized "pipeline" for processing requests to apply a model to input data
> * Scorecard models use the "re-usable alpha network" approach when possible, minimizing the use of KieSessions and rete.
> * Scorecard models use a minimal amount of rules when applying the model to input data, and any generated rules should be in executable model form/format
> * Scorecard models are applied via a service interface-
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (DROOLS-4589) Refactor of Scorecards
by Gabriele Cardosi (Jira)
[ https://issues.redhat.com/browse/DROOLS-4589?page=com.atlassian.jira.plug... ]
Gabriele Cardosi updated DROOLS-4589:
-------------------------------------
Description:
-Re-design and refactoring of Scorecard model in kie-pmml module. The result of which should be...
* Scorecard models uses a standardized "pipeline" for processing requests to apply a model to input data
* Scorecard models use the "re-usable alpha network" approach when possible, minimizing the use of KieSessions and rete.
* Scorecard models use a minimal amount of rules when applying the model to input data, and any generated rules should be in executable model form/format
* Scorecard models are -applied- via a service interface-
was:
-Re-design and refactoring of Scorecard model in kie-pmml module. The result of which should be...
* Scorecard models uses a standardized "pipeline" for processing requests to apply a model to input data
* Scorecard models use the "re-usable alpha network" approach when possible, minimizing the use of KieSessions and rete.
* Scorecard models use a minimal amount of rules when applying the model to input data, and any generated rules should be in executable model form/format
* Scorecard models are applied via a service interface-
> Refactor of Scorecards
> ----------------------
>
> Key: DROOLS-4589
> URL: https://issues.redhat.com/browse/DROOLS-4589
> Project: Drools
> Issue Type: Task
> Components: PMML
> Reporter: Lance Leverich
> Assignee: Gabriele Cardosi
> Priority: Major
> Labels: CustomerFocusTeam, TrustyAI
>
> -Re-design and refactoring of Scorecard model in kie-pmml module. The result of which should be...
> * Scorecard models uses a standardized "pipeline" for processing requests to apply a model to input data
> * Scorecard models use the "re-usable alpha network" approach when possible, minimizing the use of KieSessions and rete.
> * Scorecard models use a minimal amount of rules when applying the model to input data, and any generated rules should be in executable model form/format
> * Scorecard models are -applied- via a service interface-
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months