[JBoss JIRA] (DROOLS-2696) Dialog to name test and define bindings
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2696?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2696:
--------------------------------
Description: As a business user I want the ability to name a scenario test and define the rule bindings so that I can create a test asset. (was: As a business user I want the ability to upload an external spreadsheet so that I can speed up scenario data input.)
> Dialog to name test and define bindings
> ---------------------------------------
>
> Key: DROOLS-2696
> URL: https://issues.jboss.org/browse/DROOLS-2696
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Liz Clayton
> Assignee: Daniele Zonca
>
> As a business user I want the ability to name a scenario test and define the rule bindings so that I can create a test asset.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2696) Dialog to name test and define bindings
by Liz Clayton (JIRA)
Liz Clayton created DROOLS-2696:
-----------------------------------
Summary: Dialog to name test and define bindings
Key: DROOLS-2696
URL: https://issues.jboss.org/browse/DROOLS-2696
Project: Drools
Issue Type: Task
Components: Scenario Simulation and Testing
Reporter: Liz Clayton
Assignee: Daniele Zonca
As a business user I want the ability to upload an external spreadsheet so that I can speed up scenario data input.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFWIP-23) [Artemis 2.x upgrade] Stuck messages in artemis.internal.sf.my-cluster... queue after restarting nodes in cluster
by Michal Toth (JIRA)
[ https://issues.jboss.org/browse/WFWIP-23?page=com.atlassian.jira.plugin.s... ]
Michal Toth edited comment on WFWIP-23 at 7/2/18 1:42 PM:
----------------------------------------------------------
I am checking this one using EAP QE test suite again. Make it running 20 times.
My further tests shown error in our QE Core client, needing to handle Exception during failover.
This has been resolved.
Used {{https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/early-testing-messaging-prepare/528/artifact/jboss-eap.zip}}
{noformat}
$ ./repeat_test_until_fail.sh ClusterTestCase#testStopStartCluster
...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] jboss-hornetq-testsuite ............................ SUCCESS [ 12.403 s]
[INFO] tooling ............................................ SUCCESS [ 8.128 s]
[INFO] apps-jms11-jdk6 .................................... SUCCESS [ 1.568 s]
[INFO] tooling-eap7 ....................................... SUCCESS [ 3.895 s]
[INFO] common-tests ....................................... SUCCESS [15:20 min]
[INFO] apps-jms2 .......................................... SUCCESS [ 1.498 s]
[INFO] tests-eap7 ......................................... SUCCESS [ 7.706 s]
[INFO] apps-jms11-jdk8 .................................... SUCCESS [ 0.062 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 15:55 min
[INFO] Finished at: 2018-07-02T16:39:28+02:00
[INFO] Final Memory: 72M/1146M
[INFO] ------------------------------------------------------------------------
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 317.251 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 338.664 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 339.027 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 348.038 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 283.612 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 308.667 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 371.996 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 278.644 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 454.23 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 320.277 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 341.886 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 312.079 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 291.723 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 444.321 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,718.165 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,001.854 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 955.398 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 928.888 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 913.361 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 910.408 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
{noformat}
was (Author: mtoth):
I am checking this one using EAP QE test suite again. Make it running 20 times.
My further tests shown error in our QE Core client, needing to handle Exception during failover.
This has been resolved.
{noformat}
$ ./repeat_test_until_fail.sh ClusterTestCase#testStopStartCluster
...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] jboss-hornetq-testsuite ............................ SUCCESS [ 12.403 s]
[INFO] tooling ............................................ SUCCESS [ 8.128 s]
[INFO] apps-jms11-jdk6 .................................... SUCCESS [ 1.568 s]
[INFO] tooling-eap7 ....................................... SUCCESS [ 3.895 s]
[INFO] common-tests ....................................... SUCCESS [15:20 min]
[INFO] apps-jms2 .......................................... SUCCESS [ 1.498 s]
[INFO] tests-eap7 ......................................... SUCCESS [ 7.706 s]
[INFO] apps-jms11-jdk8 .................................... SUCCESS [ 0.062 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 15:55 min
[INFO] Finished at: 2018-07-02T16:39:28+02:00
[INFO] Final Memory: 72M/1146M
[INFO] ------------------------------------------------------------------------
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 317.251 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 338.664 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 339.027 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 348.038 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 283.612 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 308.667 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 371.996 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 278.644 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 454.23 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 320.277 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 341.886 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 312.079 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 291.723 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 444.321 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,718.165 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,001.854 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 955.398 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 928.888 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 913.361 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 910.408 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
{noformat}
> [Artemis 2.x upgrade] Stuck messages in artemis.internal.sf.my-cluster... queue after restarting nodes in cluster
> -----------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-23
> URL: https://issues.jboss.org/browse/WFWIP-23
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis
> Reporter: Miroslav Novak
> Assignee: Jiri Ondrusek
> Priority: Blocker
> Labels: activemq, feature-branch-blocker
> Attachments: journal-node-2.txt
>
>
> There are lost messages in scenario where nodes in cluster are cleanly stopped and started again. This issue was hit with Artemis 2.5.0.Final and WF Jeff's integration branch WFLY-9407_upgrade_artemis_2.4.0_with_prefix.
> Test Scenario:
> * start two servers in cluster (JGroups used for discovery)
> * send messages to testQueue0 on node-1 and node-2
> * wait until consumers on both nodes receive 300 messages
> * cleanly shut down 1st and then 2nd server
> * leave servers shut down for one minute
> * start both servers
> * wait until both consumers receive 500 messages
> * stop sending messages and receive all remaining messages
> Pass Criteria: All send messages are received by consumer
> Actual Result: There are lost messages.
> Investigation:
> There are lost messages which were sent to 2nd node. However they got stuck in queue {{.artemis.internal.sf.my-cluster.8a7e9e98-2c36-11e8-9737-fa163ea20b26}} during load balancing to 1st server.
> I'm attaching trace logs from client and servers and content of journal from 2nd server.
> This is regression against Artemis 1.5.5 thus setting blocker priority.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFWIP-23) [Artemis 2.x upgrade] Stuck messages in artemis.internal.sf.my-cluster... queue after restarting nodes in cluster
by Michal Toth (JIRA)
[ https://issues.jboss.org/browse/WFWIP-23?page=com.atlassian.jira.plugin.s... ]
Michal Toth edited comment on WFWIP-23 at 7/2/18 1:41 PM:
----------------------------------------------------------
I am checking this one using EAP QE test suite again. Make it running 20 times.
My further tests shown error in our QE Core client, needing to handle Exception during failover.
This has been resolved.
{noformat}
$ ./repeat_test_until_fail.sh ClusterTestCase#testStopStartCluster
...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] jboss-hornetq-testsuite ............................ SUCCESS [ 12.403 s]
[INFO] tooling ............................................ SUCCESS [ 8.128 s]
[INFO] apps-jms11-jdk6 .................................... SUCCESS [ 1.568 s]
[INFO] tooling-eap7 ....................................... SUCCESS [ 3.895 s]
[INFO] common-tests ....................................... SUCCESS [15:20 min]
[INFO] apps-jms2 .......................................... SUCCESS [ 1.498 s]
[INFO] tests-eap7 ......................................... SUCCESS [ 7.706 s]
[INFO] apps-jms11-jdk8 .................................... SUCCESS [ 0.062 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 15:55 min
[INFO] Finished at: 2018-07-02T16:39:28+02:00
[INFO] Final Memory: 72M/1146M
[INFO] ------------------------------------------------------------------------
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 317.251 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 338.664 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 339.027 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 348.038 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 283.612 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 308.667 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 371.996 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 278.644 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 454.23 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 320.277 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 341.886 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 312.079 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 291.723 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 444.321 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,718.165 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,001.854 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 955.398 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 928.888 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 913.361 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 910.408 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase
{noformat}
was (Author: mtoth):
I am checking this one using EAP QE test suite again. Make it running 20 times.
My further tests shown error in our QE Core client, needing to handle Exception during failover.
This has been resolved.
> [Artemis 2.x upgrade] Stuck messages in artemis.internal.sf.my-cluster... queue after restarting nodes in cluster
> -----------------------------------------------------------------------------------------------------------------
>
> Key: WFWIP-23
> URL: https://issues.jboss.org/browse/WFWIP-23
> Project: WildFly WIP
> Issue Type: Bug
> Components: Artemis
> Reporter: Miroslav Novak
> Assignee: Jiri Ondrusek
> Priority: Blocker
> Labels: activemq, feature-branch-blocker
> Attachments: journal-node-2.txt
>
>
> There are lost messages in scenario where nodes in cluster are cleanly stopped and started again. This issue was hit with Artemis 2.5.0.Final and WF Jeff's integration branch WFLY-9407_upgrade_artemis_2.4.0_with_prefix.
> Test Scenario:
> * start two servers in cluster (JGroups used for discovery)
> * send messages to testQueue0 on node-1 and node-2
> * wait until consumers on both nodes receive 300 messages
> * cleanly shut down 1st and then 2nd server
> * leave servers shut down for one minute
> * start both servers
> * wait until both consumers receive 500 messages
> * stop sending messages and receive all remaining messages
> Pass Criteria: All send messages are received by consumer
> Actual Result: There are lost messages.
> Investigation:
> There are lost messages which were sent to 2nd node. However they got stuck in queue {{.artemis.internal.sf.my-cluster.8a7e9e98-2c36-11e8-9737-fa163ea20b26}} during load balancing to 1st server.
> I'm attaching trace logs from client and servers and content of journal from 2nd server.
> This is regression against Artemis 1.5.5 thus setting blocker priority.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2563) [DMN Editor] Add support to define data-types
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2563?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2563:
--------------------------------
Issue Type: Component Upgrade Subtask (was: Sub-task)
> [DMN Editor] Add support to define data-types
> ---------------------------------------------
>
> Key: DROOLS-2563
> URL: https://issues.jboss.org/browse/DROOLS-2563
> Project: Drools
> Issue Type: Component Upgrade Subtask
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Guilherme Carreiro
>
> As a practitioner, I want to be able to define Data Types in the UI, so that when the DMN engine evaluates a decision table input/output it will check if the type of the value matches the specified type.
> Verification conditions:
> Support added for the User to define data-types ({{ItemDefinition}}).
> This may become a top-level task when I get to work on it; as the requirement is quite large and encompasses nested data-types (a whole new grid will be required); and definition of enums, constrains on values etc.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2563) [DMN Editor] Add support to define data-types
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2563?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2563:
--------------------------------
Issue Type: Sub-task (was: Component Upgrade Subtask)
> [DMN Editor] Add support to define data-types
> ---------------------------------------------
>
> Key: DROOLS-2563
> URL: https://issues.jboss.org/browse/DROOLS-2563
> Project: Drools
> Issue Type: Sub-task
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Guilherme Carreiro
>
> As a practitioner, I want to be able to define Data Types in the UI, so that when the DMN engine evaluates a decision table input/output it will check if the type of the value matches the specified type.
> Verification conditions:
> Support added for the User to define data-types ({{ItemDefinition}}).
> This may become a top-level task when I get to work on it; as the requirement is quite large and encompasses nested data-types (a whole new grid will be required); and definition of enums, constrains on values etc.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2563) [DMN Editor] Add support to define data-types
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2563?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-2563:
-------------------------------------
p.s. I added a user story just as a test, not sure if it's accurate or not...
> [DMN Editor] Add support to define data-types
> ---------------------------------------------
>
> Key: DROOLS-2563
> URL: https://issues.jboss.org/browse/DROOLS-2563
> Project: Drools
> Issue Type: Sub-task
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Guilherme Carreiro
>
> As a practitioner, I want to be able to define Data Types in the UI, so that when the DMN engine evaluates a decision table input/output it will check if the type of the value matches the specified type.
> Verification conditions:
> Support added for the User to define data-types ({{ItemDefinition}}).
> This may become a top-level task when I get to work on it; as the requirement is quite large and encompasses nested data-types (a whole new grid will be required); and definition of enums, constrains on values etc.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2563) [DMN Editor] Add support to define data-types
by Liz Clayton (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2563?page=com.atlassian.jira.plugi... ]
Liz Clayton updated DROOLS-2563:
--------------------------------
Description:
As a practitioner, I want to be able to define Data Types in the UI, so that when the DMN engine evaluates a decision table input/output it will check if the type of the value matches the specified type.
Verification conditions:
Support added for the User to define data-types ({{ItemDefinition}}).
This may become a top-level task when I get to work on it; as the requirement is quite large and encompasses nested data-types (a whole new grid will be required); and definition of enums, constrains on values etc.
was:
Add support for the User to define data-types ({{ItemDefinition}}).
This may become a top-level task when I get to work on it; as the requirement is quite large and encompasses nested data-types (a whole new grid will be required); and definition of enums, constrains on values etc.
> [DMN Editor] Add support to define data-types
> ---------------------------------------------
>
> Key: DROOLS-2563
> URL: https://issues.jboss.org/browse/DROOLS-2563
> Project: Drools
> Issue Type: Sub-task
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Guilherme Carreiro
>
> As a practitioner, I want to be able to define Data Types in the UI, so that when the DMN engine evaluates a decision table input/output it will check if the type of the value matches the specified type.
> Verification conditions:
> Support added for the User to define data-types ({{ItemDefinition}}).
> This may become a top-level task when I get to work on it; as the requirement is quite large and encompasses nested data-types (a whole new grid will be required); and definition of enums, constrains on values etc.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2695) Beta node indexes don't support type coercion
by Mario Fusco (JIRA)
Mario Fusco created DROOLS-2695:
-----------------------------------
Summary: Beta node indexes don't support type coercion
Key: DROOLS-2695
URL: https://issues.jboss.org/browse/DROOLS-2695
Project: Drools
Issue Type: Bug
Components: core engine
Reporter: Mario Fusco
Assignee: Mario Fusco
When there is a type mismatch (e.g. String vs Integer) in a constraint, usually a type is coerced and a rule is fired.
{code}
rule "R2"
when
$f : MyFactB( strData == 20 )
then
System.out.println( "R2 fired : $f = " + $f );
end
{code}
As far as I investigate, in case of AlphaNode, MVEL does the coercion. Also AlphaNode hashing does the coercion (https://github.com/kiegroup/drools/blob/7.5.0.Final/drools-core/src/main/...).
However, in case of JoinNode, it doesn't coerce so doesn't fire.
{code}
rule "R1"
when
MyFactA( $i : intData )
$f : MyFactB( strData == $i )
then
System.out.println( "R1 fired : $f = " + $f );
end
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years