[JBoss JIRA] (DROOLS-1466) Bound fields when changed in the WHEN condition become uneditable after saving
by Saurabh Sharma (JIRA)
Saurabh Sharma created DROOLS-1466:
--------------------------------------
Summary: Bound fields when changed in the WHEN condition become uneditable after saving
Key: DROOLS-1466
URL: https://issues.jboss.org/browse/DROOLS-1466
Project: Drools
Issue Type: Bug
Components: tools
Affects Versions: 6.4.0.Final
Environment: IBM WebSphere Application Server Network
Deployment 8.5.5.9 (64-bit)
Reporter: Saurabh Sharma
Assignee: Mario Fusco
Priority: Minor
Attachments: SimpleRule.jpg, SimpleRuleEdit.jpg
Calculation of a mid price of an instrument
While defining the WHEN condition, when a new price (NEWPRC) is bound from GSO.newPrice
The required fields for that price is bound so that they can be changed in the THEN condition.
The properties of the price are similar to any of the Bid or the Ask price except the unit price value. Those values are bound as well in the rule WHEN condition, and used in the
THEN clause.
In the THEN condition, the individual bound variables are set with values, the UI lets me add those values correctly without any issues the first time around.
The problem occurs when the rule is saved, and opened again for editing. All the fields become uneditable and i have to repeat the steps of binding the variables of
NEWPRC and then modify/set the values of those variables again in the WHEN condition.
Is there any way to open the rule and get those bound variables in the edit mode
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (DROOLS-1465) not() unary test is short circuiting in the presence of null
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1465?page=com.atlassian.jira.plugi... ]
Edson Tirelli updated DROOLS-1465:
----------------------------------
Description:
not() unary tests as it is short-circuiting in some cases without checking all the elements. E.g.:
10 in ( not( null, 10 ) ) ----> short circuits and returns true when it should be false
null in ( not( 10, null ) ) -----> short circuits and returns true when it should be false
was:
Grammar rule #17 prevents not() from being used as part of a unary test list. Needs to be fixed in the engine.
Also, there seems to be a bug on the creation of not() unary tests as it is short-circuiting in some cases without checking all the elements.
> not() unary test is short circuiting in the presence of null
> ------------------------------------------------------------
>
> Key: DROOLS-1465
> URL: https://issues.jboss.org/browse/DROOLS-1465
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Affects Versions: 7.0.0.Beta6
> Reporter: Edson Tirelli
> Assignee: Edson Tirelli
> Fix For: 7.0.0.Final
>
>
> not() unary tests as it is short-circuiting in some cases without checking all the elements. E.g.:
> 10 in ( not( null, 10 ) ) ----> short circuits and returns true when it should be false
> null in ( not( 10, null ) ) -----> short circuits and returns true when it should be false
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (DROOLS-1465) not() unary test is short circuiting in the presence of null
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1465?page=com.atlassian.jira.plugi... ]
Edson Tirelli updated DROOLS-1465:
----------------------------------
Summary: not() unary test is short circuiting in the presence of null (was: FEEL grammar does not accept not() as an element in a list of unit tests)
> not() unary test is short circuiting in the presence of null
> ------------------------------------------------------------
>
> Key: DROOLS-1465
> URL: https://issues.jboss.org/browse/DROOLS-1465
> Project: Drools
> Issue Type: Bug
> Components: dmn engine
> Affects Versions: 7.0.0.Beta6
> Reporter: Edson Tirelli
> Assignee: Edson Tirelli
> Fix For: 7.0.0.Final
>
>
> Grammar rule #17 prevents not() from being used as part of a unary test list. Needs to be fixed in the engine.
> Also, there seems to be a bug on the creation of not() unary tests as it is short-circuiting in some cases without checking all the elements.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8300) standalone-picketlink.xml boots with lots of errors
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-8300?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-8300:
-----------------------------------
Sadly testsuite doesn't alter it that much at all.
It is actually testing it that it works.
Alteration that are done are only related ipv4 --> ipv6 changes to make it work in both scenarios.
In a way the example picketlink config is more of testsuite config than any thing else.
Also bit bad one at it, as it doesn't test some scenarios that would definitely fail as it doesn't boot all services right.
> standalone-picketlink.xml boots with lots of errors
> ---------------------------------------------------
>
> Key: WFLY-8300
> URL: https://issues.jboss.org/browse/WFLY-8300
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Tomaz Cerar
> Assignee: Darran Lofthouse
>
> If you try to run standalone-picketlink.xml server configuration, it's boot fails with lots of problems. They look related to elytron changes, but I am not sure.
> {noformat}
> 15:27:36,476 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "picketlink-identity-management"),
> ("partition-manager" => "jpa.emf.modules.partition.manager")
> ]) - failure description: {
> "WFLYCTL0080: Failed services" => {"jboss.picketlink-identity-management.\"jpa.emf.modules.partition.manager\".\"jpa.config\".jpa-store" => "org.jboss.msc.service.StartException in service jb
> oss.picketlink-identity-management.\"jpa.emf.modules.partition.manager\".\"jpa.config\".jpa-store: Failed to start service
> Caused by: org.picketlink.idm.config.SecurityConfigurationException: WFLYPL0050: Entities module not found [my.module]."},
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.picketlink-identity-management.\"jpa.emf.modules.partition.manager\".\"jpa.config\".jpa-store"]
> }
> 15:27:36,477 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "undertow"),
> ("server" => "default-server"),
> ("host" => "default-host"),
> ("setting" => "http-invoker")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.http-authentication-factory.application-http-authentication"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.undertow.server.default-server.default-host.http-invoker is missing [org.wildfly.security.http-authentication-factory.
> application-http-authentication]"]
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (DROOLS-1465) FEEL grammar does not accept not() as an element in a list of unit tests
by Edson Tirelli (JIRA)
Edson Tirelli created DROOLS-1465:
-------------------------------------
Summary: FEEL grammar does not accept not() as an element in a list of unit tests
Key: DROOLS-1465
URL: https://issues.jboss.org/browse/DROOLS-1465
Project: Drools
Issue Type: Bug
Components: dmn engine
Affects Versions: 7.0.0.Beta6
Reporter: Edson Tirelli
Assignee: Edson Tirelli
Fix For: 7.0.0.Final
Grammar rule #17 prevents not() from being used as part of a unary test list. Needs to be fixed in the engine.
Also, there seems to be a bug on the creation of not() unary tests as it is short-circuiting in some cases without checking all the elements.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8300) standalone-picketlink.xml boots with lots of errors
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-8300?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-8300:
----------------------------------------
Sure; I was unclear. I don't mean not to do anything at all about this. I'm just pointing at that IIRC the config was never directly bootable so people looking at this shouldn't get confused and go off "fixing" stuff that was never meant to work. I assume the testsuite was doing something to alter the config before trying to use it.
> standalone-picketlink.xml boots with lots of errors
> ---------------------------------------------------
>
> Key: WFLY-8300
> URL: https://issues.jboss.org/browse/WFLY-8300
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Tomaz Cerar
> Assignee: Darran Lofthouse
>
> If you try to run standalone-picketlink.xml server configuration, it's boot fails with lots of problems. They look related to elytron changes, but I am not sure.
> {noformat}
> 15:27:36,476 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "picketlink-identity-management"),
> ("partition-manager" => "jpa.emf.modules.partition.manager")
> ]) - failure description: {
> "WFLYCTL0080: Failed services" => {"jboss.picketlink-identity-management.\"jpa.emf.modules.partition.manager\".\"jpa.config\".jpa-store" => "org.jboss.msc.service.StartException in service jb
> oss.picketlink-identity-management.\"jpa.emf.modules.partition.manager\".\"jpa.config\".jpa-store: Failed to start service
> Caused by: org.picketlink.idm.config.SecurityConfigurationException: WFLYPL0050: Entities module not found [my.module]."},
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.picketlink-identity-management.\"jpa.emf.modules.partition.manager\".\"jpa.config\".jpa-store"]
> }
> 15:27:36,477 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "undertow"),
> ("server" => "default-server"),
> ("host" => "default-host"),
> ("setting" => "http-invoker")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.http-authentication-factory.application-http-authentication"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.undertow.server.default-server.default-host.http-invoker is missing [org.wildfly.security.http-authentication-factory.
> application-http-authentication]"]
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (DROOLS-1464) Unary tests raising NPE on null input
by Edson Tirelli (JIRA)
Edson Tirelli created DROOLS-1464:
-------------------------------------
Summary: Unary tests raising NPE on null input
Key: DROOLS-1464
URL: https://issues.jboss.org/browse/DROOLS-1464
Project: Drools
Issue Type: Bug
Components: dmn engine
Affects Versions: 7.0.0.Beta6
Reporter: Edson Tirelli
Assignee: Edson Tirelli
Fix For: 7.0.0.Final
Some unary tests are raising NPE on null input. E.g.:
```UnaryTestNode{ < 0 }```
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8303) Clustering testsuite: Remove XSLTs in favor of executing CLI scripts via wildfly-maven-plugin
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-8303?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-8303:
------------------------------
Description:
i.e.
{code:xml}
<plugin>
<groupId>org.wildfly.plugins</groupId>
<artifactId>wildfly-maven-plugin</artifactId>
<version>${version.org.wildfly.plugin}</version>
<executions>
<execution>
<phase>process-test-resources</phase>
<goals>
<goal>execute-commands</goal>
</goals>
</execution>
</executions>
<configuration>
<offline>true</offline>
<scripts>
<script>setup-network.cli</script>
<script>modify-cache-mode.cli</script>
<script>...</script>
</scripts>
<jboss-home>${wildfly.dir}</jboss-home>
<stdout>${project.build.directory}/wildfly-plugin.log</stdout>
<system-properties>
<public.ip>${node0}</public.ip>
<management.ip>${node0}</management.ip>
...
{code}
was:
i.e.
{code:xml}
<plugin>
<groupId>org.wildfly.plugins</groupId>
<artifactId>wildfly-maven-plugin</artifactId>
<version>${version.org.wildfly.plugin}</version>
<executions>
<execution>
<phase>process-test-resources</phase>
<goals>
<goal>execute-commands</goal>
</goals>
</execution>
</executions>
<configuration>
<offline>true</offline>
<scripts>
<script>modify-cache-mode.cli</script>
</scripts>
<jboss-home>${wildfly.dir}</jboss-home>
<stdout>${project.build.directory}/wildfly-plugin.log</stdout>
<system-properties>
<public.ip>${node0}</public.ip>
<management.ip>${node0}</management.ip>
...
{code}
> Clustering testsuite: Remove XSLTs in favor of executing CLI scripts via wildfly-maven-plugin
> ---------------------------------------------------------------------------------------------
>
> Key: WFLY-8303
> URL: https://issues.jboss.org/browse/WFLY-8303
> Project: WildFly
> Issue Type: Task
> Components: Clustering, Test Suite
> Affects Versions: 10.1.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
>
> i.e.
> {code:xml}
> <plugin>
> <groupId>org.wildfly.plugins</groupId>
> <artifactId>wildfly-maven-plugin</artifactId>
> <version>${version.org.wildfly.plugin}</version>
> <executions>
> <execution>
> <phase>process-test-resources</phase>
> <goals>
> <goal>execute-commands</goal>
> </goals>
> </execution>
> </executions>
> <configuration>
> <offline>true</offline>
> <scripts>
> <script>setup-network.cli</script>
> <script>modify-cache-mode.cli</script>
> <script>...</script>
> </scripts>
> <jboss-home>${wildfly.dir}</jboss-home>
> <stdout>${project.build.directory}/wildfly-plugin.log</stdout>
> <system-properties>
> <public.ip>${node0}</public.ip>
> <management.ip>${node0}</management.ip>
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8291) mod_cluster operation descriptions only refer to Apache httpd
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-8291?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-8291:
---------------------------------
Summary: mod_cluster operation descriptions only refer to Apache httpd (was: Mod_cluster operation descriptions only refer to Apache httpd)
> mod_cluster operation descriptions only refer to Apache httpd
> -------------------------------------------------------------
>
> Key: WFLY-8291
> URL: https://issues.jboss.org/browse/WFLY-8291
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 10.1.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Minor
>
> Please repair description in following operations as they are outdated, undertow proxy
> is able to process this messages.
> {noformat}
> {
> "outcome" => "success",
> "result" => {
> "operation-name" => "disable",
> "description" => "Tell Apache httpd that all contexts of the node can't process new requests.",
> "request-properties" => {},
> "reply-properties" => {},
> "read-only" => false,
> "runtime-only" => true
> }
> }
> {noformat}
> {noformat}
> {
> "outcome" => "success",
> "result" => {
> "operation-name" => "disable-context",
> "description" => "Tell Apache httpd that the context can't process new requests.",
> "request-properties" => {
> "virtualhost" => {
> "type" => STRING,
> "description" => "virtual host",
> "expressions-allowed" => false,
> "required" => true,
> "nillable" => false,
> "min-length" => 1L,
> "max-length" => 2147483647L
> },
> "context" => {
> "type" => STRING,
> "description" => "context",
> "expressions-allowed" => false,
> "required" => true,
> "nillable" => false,
> "min-length" => 1L,
> "max-length" => 2147483647L
> }
> },
> "reply-properties" => {},
> "read-only" => false,
> "runtime-only" => true
> }
> }
> {noformat}
> {noformat}
> {
> "outcome" => "success",
> "result" => {
> "operation-name" => "enable",
> "description" => "Tell Apache httpd that all contexts of the node are ready receive requests.",
> "request-properties" => {},
> "reply-properties" => {},
> "read-only" => false,
> "runtime-only" => true
> }
> }
> {noformat}
> {noformat}
> {
> "outcome" => "success",
> "result" => {
> "operation-name" => "enable-context",
> "description" => "Tell Apache httpd that the context is ready receive requests.",
> "request-properties" => {
> "virtualhost" => {
> "type" => STRING,
> "description" => "Virtual host",
> "expressions-allowed" => false,
> "required" => true,
> "nillable" => false,
> "min-length" => 1L,
> "max-length" => 2147483647L
> },
> "context" => {
> "type" => STRING,
> "description" => "Context",
> "expressions-allowed" => false,
> "required" => true,
> "nillable" => false,
> "min-length" => 1L,
> "max-length" => 2147483647L
> }
> },
> "reply-properties" => {},
> "read-only" => false,
> "runtime-only" => true
> }
> }
> {noformat}
> {noformat}
> {
> "outcome" => "success",
> "result" => {
> "operation-name" => "stop",
> "description" => "Tell Apache httpd that all contexts of the node can't process requests.",
> "request-properties" => {"waittime" => {
> "type" => INT,
> "description" => "wait timeout",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "default" => 10,
> "unit" => "SECONDS"
> }},
> "reply-properties" => {},
> "read-only" => false,
> "runtime-only" => true
> }
> }
> {noformat}
> {noformat}
> {
> "outcome" => "success",
> "result" => {
> "operation-name" => "stop-context",
> "description" => "Tell Apache httpd that the context can't process requests.",
> "request-properties" => {
> "virtualhost" => {
> "type" => STRING,
> "description" => "Virtual host",
> "expressions-allowed" => false,
> "required" => true,
> "nillable" => false,
> "min-length" => 1L,
> "max-length" => 2147483647L
> },
> "context" => {
> "type" => STRING,
> "description" => "Context",
> "expressions-allowed" => false,
> "required" => true,
> "nillable" => false,
> "min-length" => 1L,
> "max-length" => 2147483647L
> },
> "waittime" => {
> "type" => INT,
> "description" => "wait timeout",
> "expressions-allowed" => false,
> "required" => false,
> "nillable" => true,
> "default" => 10,
> "unit" => "SECONDS"
> }
> },
> "reply-properties" => {},
> "read-only" => false,
> "runtime-only" => true
> }
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8304) mod_cluster max-attempts minimal value
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-8304?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-8304:
---------------------------------
Summary: mod_cluster max-attempts minimal value (was: Max-attempts minimal value)
> mod_cluster max-attempts minimal value
> --------------------------------------
>
> Key: WFLY-8304
> URL: https://issues.jboss.org/browse/WFLY-8304
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 10.1.0.Final
> Reporter: Bogdan Sikora
> Assignee: Radoslav Husar
> Priority: Minor
>
> [Documentation|http://modcluster.io/documentation/#proxy-configuration-1]
> {noformat}
> Maximum number of failover attempts before giving up. The minimum value is 0, i.e. no failover. The default value is 1, i.e. do a one failover attempt.
> {noformat}
> Max-attemps minimal value is
> {noformat}
> "max-attempts" => {
> "type" => INT,
> "description" => "Max attempts to process an idempotent request.",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => 1,
> "min" => -1L,
> "max" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> {noformat}
> Min value to 0. In the mod_cluster subsystem(worker side).
> And max-attemps handling on the balancer side. Balancer has minimal value of 1 and therefore any value lower than that is ignored. Should be 0.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months