January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2853) Make DMN Verifier in UI use the experimental tag

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-2853?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-2853: --------------------------------- Summary: Make DMN Verifier in UI use the experimental tag (was: Make DMN Verifier use the experimental tag) > Make DMN Verifier in UI use the experimental tag > ------------------------------------------------ > > Key: DROOLS-2853 > URL: https://issues.jboss.org/browse/DROOLS-2853 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor, verifier > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Optional > Labels: drools-tools, verifier > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2853) Make DMN Verifier use the experimental tag

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-2853?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-2853: --------------------------------- Priority: Optional (was: Major) > Make DMN Verifier use the experimental tag > ------------------------------------------ > > Key: DROOLS-2853 > URL: https://issues.jboss.org/browse/DROOLS-2853 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor, verifier > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Optional > Labels: drools-tools, verifier > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3094) Create a Verifier backend adapter for DMN tables

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-3094?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-3094: --------------------------------- Priority: Optional (was: Major) > Create a Verifier backend adapter for DMN tables > ------------------------------------------------ > > Key: DROOLS-3094 > URL: https://issues.jboss.org/browse/DROOLS-3094 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Optional > Labels: verifier > > The goal is to make it possible to run the DMN Validation using the DMN backend validate-method. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3094) Create a Verifier backend adapter for DMN tables

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-3094?page=com.atlassian.jira.plugi... ] Toni Rikkola commented on DROOLS-3094: -------------------------------------- [~tarilabs] Hi do you have another ticket with the same coverage? > Create a Verifier backend adapter for DMN tables > ------------------------------------------------ > > Key: DROOLS-3094 > URL: https://issues.jboss.org/browse/DROOLS-3094 > Project: Drools > Issue Type: Feature Request > Components: DMN Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: verifier > > The goal is to make it possible to run the DMN Validation using the DMN backend validate-method. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3486) Scenario Simulation: Export agenda info from session to a report

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3486?page=com.atlassian.jira.plugi... ] Klara Kufova commented on DROOLS-3486: -------------------------------------- [~aglass], thank you for the question! I added the tags during our planning meeting to make sure this won't slip through the cracks. I created a new Jira just for the UX team: DROOLS-3516. Feel free to close the Jira in case you decide it is not needed after all. Regarding the task itself, please reach out to [~Rikkola] or [~danielezonca] in case you or Tao need more detailed information to start working on it. > Scenario Simulation: Export agenda info from session to a report > ---------------------------------------------------------------- > > Key: DROOLS-3486 > URL: https://issues.jboss.org/browse/DROOLS-3486 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: ScenarioSimulation > > Report information should at least contain information about test coverage and what rules fired and what not. Proposed format is CSV file. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3283) Incorrect V&V results when operator is filled in the row (as opposed to column definition)

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-3283?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-3283: --------------------------------- Priority: Critical (was: Major) > Incorrect V&V results when operator is filled in the row (as opposed to column definition) > ------------------------------------------------------------------------------------------ > > Key: DROOLS-3283 > URL: https://issues.jboss.org/browse/DROOLS-3283 > Project: Drools > Issue Type: Bug > Affects Versions: 7.14.0.Final > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Critical > Labels: drools-tools, support, verifier > > Imagine data model Person with attribute age. > If you create decision table and add two columns: > - both are defined against "age" attribute > - none of them have operator defined > then you add one row, and you fill in the operator and the value directly inside the row. > For example: > >= 20 > <= 30 > The generated DRL looks like this: > {code:java} > package org; > //from row number: 1 > rule "Row 1 AnotherTest" > dialect "mvel" > when > p : Person( age >= 20 , age <= 30 ) > then > p.setAgeGroup( "whatever" ); > end > {code} > The V&V will report this as conflicting row: > !6iOx.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3486) Scenario Simulation: Export agenda info from session to a report

by Klara Kufova (Jira)

[ https://issues.jboss.org/browse/DROOLS-3486?page=com.atlassian.jira.plugi... ] Klara Kufova updated DROOLS-3486: --------------------------------- Labels: ScenarioSimulation (was: ) > Scenario Simulation: Export agenda info from session to a report > ---------------------------------------------------------------- > > Key: DROOLS-3486 > URL: https://issues.jboss.org/browse/DROOLS-3486 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: ScenarioSimulation > > Report information should at least contain information about test coverage and what rules fired and what not. Proposed format is CSV file. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4274) SuspendResumeTestCase fails sometimes

by Richard Opalka (Jira)

Richard Opalka created WFCORE-4274: -------------------------------------- Summary: SuspendResumeTestCase fails sometimes Key: WFCORE-4274 URL: https://issues.jboss.org/browse/WFCORE-4274 Project: WildFly Core Issue Type: Bug Components: Test Suite Affects Versions: 8.0.0.Beta2 Reporter: Richard Opalka Fix For: 8.0.0.Beta3 [INFO] Running org.wildfly.core.test.standalone.suspend.web.SuspendResumeTestCase [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.076 s <<< FAILURE! - in org.wildfly.core.test.standalone.suspend.web.SuspendResumeTestCase [ERROR] testSuspendResume(org.wildfly.core.test.standalone.suspend.web.SuspendResumeTestCase) Time elapsed: 1.046 s <<< FAILURE! org.junit.ComparisonFailure: expected:<SUSPEND[ED]> but was:<SUSPEND[ING]> at org.junit.Assert.assertEquals(Assert.java:115) at org.junit.Assert.assertEquals(Assert.java:144) at org.wildfly.core.test.standalone.suspend.web.SuspendResumeTestCase.testSuspendResume(SuspendResumeTestCase.java:116) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:109) at org.junit.runners.Suite.runChild(Suite.java:128) at org.junit.runners.Suite.runChild(Suite.java:27) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83) at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75) at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344) at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3513) [DMN Designer] Literal expression boxes can not be changed in height

by Thomas Mantegazzi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3513?page=com.atlassian.jira.plugi... ] Thomas Mantegazzi updated DROOLS-3513: -------------------------------------- Summary: [DMN Designer] Literal expression boxes can not be changed in height (was: [DMN Designer] Literal expression boxes can not be changed in haing) > [DMN Designer] Literal expression boxes can not be changed in height > -------------------------------------------------------------------- > > Key: DROOLS-3513 > URL: https://issues.jboss.org/browse/DROOLS-3513 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.15.0.Final > Reporter: Thomas Mantegazzi > Assignee: Michael Anstis > Priority: Major > Attachments: image-2019-01-14-09-12-40-849.png > > > If a more complex logic is inputed in a literal expression, it might be thate the literal expression becomes more than a few lines. At the moment it is not possible to resize the heignt of the literal expression box. > !image-2019-01-14-09-12-40-849.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3515) [DMN Designer] Validation does not check feel expressions.

by Thomas Mantegazzi (Jira)

Thomas Mantegazzi created DROOLS-3515: ----------------------------------------- Summary: [DMN Designer] Validation does not check feel expressions. Key: DROOLS-3515 URL: https://issues.jboss.org/browse/DROOLS-3515 Project: Drools Issue Type: Bug Components: DMN Editor Reporter: Thomas Mantegazzi Assignee: Michael Anstis Attachments: image-2019-01-14-09-24-07-415.png, image-2019-01-14-09-25-01-777.png, image-2019-01-14-09-25-16-907.png The "validate" button at the top does nit seem to be validating feel expressions: !image-2019-01-14-09-24-07-415.png|thumbnail! The input of this Decision is a "person" object: !image-2019-01-14-09-25-01-777.png|thumbnail! and this is the DRG: !image-2019-01-14-09-25-16-907.png|thumbnail! The validation should say that this literal expression is not valid. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2019