December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3096) Postponed after MVP

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-3096?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-3096: ------------------------------------ Labels: ScenarioSimulation drools-tools (was: ScenarioSimulation) > Postponed after MVP > ------------------- > > Key: DROOLS-3096 > URL: https://issues.redhat.com/browse/DROOLS-3096 > Project: Drools > Issue Type: Epic > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation, drools-tools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4435) Test Scenario: add validation during file loading to avoid an additional backend call

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4435?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4435: ------------------------------------ Labels: ScenarioSimulation drools-tools (was: ScenarioSimulation) > Test Scenario: add validation during file loading to avoid an additional backend call > ------------------------------------------------------------------------------------- > > Key: DROOLS-4435 > URL: https://issues.redhat.com/browse/DROOLS-4435 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation, drools-tools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3391) UI should select and highlight grid cells with menus.

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-3391?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-3391: ------------------------------------ Labels: ScenarioSimulation UX UXTeam drools-tools (was: ScenarioSimulation UX UXTeam) > UI should select and highlight grid cells with menus. > ------------------------------------------------------ > > Key: DROOLS-3391 > URL: https://issues.redhat.com/browse/DROOLS-3391 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Elizabeth Clayton > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam, drools-tools > > Grid cell with actions (contextual menus, pop-overs, etc.) should visually indicate a cell selection state (blue border) - both for usability and to align withAlign with DMN and GDT. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3240) Cross-editor UX Consistency

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-3240?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-3240: ------------------------------------ Labels: UX UXTeam drools-tools (was: UX UXTeam) > Cross-editor UX Consistency > --------------------------- > > Key: DROOLS-3240 > URL: https://issues.redhat.com/browse/DROOLS-3240 > Project: Drools > Issue Type: Epic > Components: DMN Editor, Guided Decision Table Editor, Test Scenarios Editor > Reporter: Ivo Bek > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > > We have quite a few tasks to ensure UX consistency across multiple editors - DMN Modeler, Guided Decision Tables, Test Scenario tool, etc. > This epic links to and oversee such UX work efforts so that the scrum teams are aware of the changes that will make all the editors consistent. > https://docs.google.com/document/d/1ZXlOjR-bI-Bkkusn-CA3f-0ILyyh8tSZY1hg5... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1985) Test Scenario fails to populate Date field

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-1985?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-1985: ------------------------------------ Labels: drools-tools (was: ) > Test Scenario fails to populate Date field > ------------------------------------------ > > Key: DROOLS-1985 > URL: https://issues.redhat.com/browse/DROOLS-1985 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Affects Versions: 5.5.0.Final > Reporter: Toshiya Kobayashi > Assignee: Mark Coble > Priority: Major > Labels: drools-tools > Attachments: repository_export_mvel_date.zip > > > Under the conditions: > - Model A has a Date field > - Model B extends Model A > - All rules have "java" dialect > When you set a value to the Date field of Model B in a Test Scenario, the Test scenario fails to run and throws the Exception. > {noformat} > 20:59:23,323 INFO [stdout] (http--127.0.0.1-8080-1) ERROR 14-11 20:59:23,322 (LoggingHelper.java:error:74) Unable to run the scenario. > 20:59:23,323 INFO [stdout] (http--127.0.0.1-8080-1) [Error: could not access/write property (dateTime) in: defaultPackage.SubModel] > 20:59:23,323 INFO [stdout] (http--127.0.0.1-8080-1) [Near : {... __fact__.dateTime= __val__ ....}] > 20:59:23,324 INFO [stdout] (http--127.0.0.1-8080-1) ^ > 20:59:23,324 INFO [stdout] (http--127.0.0.1-8080-1) [Line: 1, Column: 1] > 20:59:23,324 INFO [stdout] (http--127.0.0.1-8080-1) at org.mvel2.PropertyAccessor.set(PropertyAccessor.java:372) > 20:59:23,324 INFO [stdout] (http--127.0.0.1-8080-1) at org.mvel2.PropertyAccessor.set(PropertyAccessor.java:139) > 20:59:23,324 INFO [stdout] (http--127.0.0.1-8080-1) at org.mvel2.ast.DeepAssignmentNode.getReducedValue(DeepAssignmentNode.java:97) > 20:59:23,324 INFO [stdout] (http--127.0.0.1-8080-1) at org.mvel2.MVELInterpretedRuntime.parseAndExecuteInterpreted(MVELInterpretedRuntime.java:106) > 20:59:23,324 INFO [stdout] (http--127.0.0.1-8080-1) at org.mvel2.MVELInterpretedRuntime.parse(MVELInterpretedRuntime.java:49) > 20:59:23,324 INFO [stdout] (http--127.0.0.1-8080-1) at org.mvel2.MVEL.eval(MVEL.java:165) > 20:59:23,324 INFO [stdout] (http--127.0.0.1-8080-1) at org.drools.ide.common.server.testscenarios.populators.FieldPopulator.populateField(FieldPopulator.java:47) > 20:59:23,324 INFO [stdout] (http--127.0.0.1-8080-1) at org.drools.ide.common.server.testscenarios.populators.SimpleFieldPopulator.populate(SimpleFieldPopulator.java:35) > 20:59:23,325 INFO [stdout] (http--127.0.0.1-8080-1) at org.drools.ide.common.server.testscenarios.populators.FactPopulator.populate(FactPopulator.java:52) > 20:59:23,325 INFO [stdout] (http--127.0.0.1-8080-1) at org.drools.ide.common.server.testscenarios.ScenarioRunner.applyFixtures(ScenarioRunner.java:119) > 20:59:23,325 INFO [stdout] (http--127.0.0.1-8080-1) at org.drools.ide.common.server.testscenarios.ScenarioRunner.run(ScenarioRunner.java:82) > 20:59:23,325 INFO [stdout] (http--127.0.0.1-8080-1) at org.drools.guvnor.server.TestScenarioServiceImplementation.runScenario(TestScenarioServiceImplementation.java:160) > 20:59:23,325 INFO [stdout] (http--127.0.0.1-8080-1) at org.drools.guvnor.server.TestScenarioServiceImplementation.runScenario(TestScenarioServiceImplementation.java:111) > 20:59:23,325 INFO [stdout] (http--127.0.0.1-8080-1) at org.drools.guvnor.server.TestScenarioServiceImplementation.runScenario(TestScenarioServiceImplementation.java:101) > 20:59:23,325 INFO [stdout] (http--127.0.0.1-8080-1) at org.drools.guvnor.server.TestScenarioServiceServlet.runScenario(TestScenarioServiceServlet.java:39) > {noformat} > This is because org.drools.ide.common.server.testscenarios.populators.FieldPopulatorFactory.isDate() uses Class.getDeclaredMethods which doesn't return super class methods. > {code:java} > private boolean isDate(String fieldName) { > for (Method method : factObject.getClass().getDeclaredMethods()) { > if (hasMutator(fieldName, method)) { > if (java.util.Date.class.isAssignableFrom(method.getParameterTypes()[0])) { > return true; > } > } > } > return false; > } > {code} > BTW, if your rules use "mvel" dialect, Guvnor will load org.drools.base.mvel.MVELCompilationUnit class and its static block registers for Date and Calendar org.mvel2.DataConversion. Hence this issue will not occur. > {code:java} > static { > //for handling dates as string literals > DataConversion.addConversionHandler( Date.class, > new MVELDateCoercion() ); > DataConversion.addConversionHandler( Calendar.class, > new MVELCalendarCoercion() ); > } > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4799) Adding "expression" type handling for Collection type propereties

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4799?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4799: ------------------------------------ Labels: UX UXTeam drools-tools (was: UX UXTeam) > Adding "expression" type handling for Collection type propereties > ----------------------------------------------------------------- > > Key: DROOLS-4799 > URL: https://issues.redhat.com/browse/DROOLS-4799 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Yeser Amer > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2019-11-26 at 1.26.54 PM.png, dmn-dt-enumeration-constraint.png, dmn-dt-expression-constraint.png, expression-list_error.png, scesim-list.png > > > I need a clarification regarding the behaviour of the updated Collection Editor, in particular for this section -->https://marvelapp.com/5ab248j/screen/62093042/layer/102496330. > Considering the editor introduces a new way to handle a Collection ("Define List"), can you please give us detailed behaviour for the following case: > - What happen if a user starts to input data inside a section (Define List/Create List) and then switch on the other one? > eg. if I start to define a List using "Define List" option (i.e. an expression) and then I change to "Create List" case. What should happen? > - Currently, after adding a Collection, the Grid cell will show "List (1)". It should be the same for "Define list" (i.e. Expression) case? > In case of additional clarificaiton, I'll update this ticket. > Hope it's clear, if not you can contact me anytime. > Thanks -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4663) Scenario Background Table validation

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4663?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4663: ------------------------------------ Labels: drools-tools (was: ) > Scenario Background Table validation > ------------------------------------ > > Key: DROOLS-4663 > URL: https://issues.redhat.com/browse/DROOLS-4663 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing > Affects Versions: 7.29.0.Final > Reporter: Jozef Marko > Assignee: Gabriele Cardosi > Priority: Major > Labels: drools-tools > > Currently the Scenario Background table validation doesn't work, for more details, see the [comment|https://github.com/kiegroup/drools-wb/pull/1239#issuecomment-5436...]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4585) Focus doesn't moves after the selected cell

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-4585?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-4585: ------------------------------------ Labels: CustomerFocus drools-tools (was: CustomerFocus) > Focus doesn't moves after the selected cell > ------------------------------------------- > > Key: DROOLS-4585 > URL: https://issues.redhat.com/browse/DROOLS-4585 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.28.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Major > Labels: CustomerFocus, drools-tools > > {color:red}*Failure*{color} > If you navigate cell that is obscured by the right panel in header then it dosen't automatically scrolls to it as it done for grid body. > *Expected* > Viewed part of grid follows the selected cell -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3879) Create Kogito version of Test Scenarios designer

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-3879?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-3879: ------------------------------------ Labels: drools-tools (was: ) > Create Kogito version of Test Scenarios designer > ------------------------------------------------ > > Key: DROOLS-3879 > URL: https://issues.redhat.com/browse/DROOLS-3879 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: drools-tools > > Create the *Kogito* versions of scesim editor. > No Home Page, no Library, No preferences, no other editors. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3422) Validate scenario dmn import validation

by Guilherme Gomes (Jira)

[ https://issues.redhat.com/browse/DROOLS-3422?page=com.atlassian.jira.plug... ] Guilherme Gomes updated DROOLS-3422: ------------------------------------ Labels: drools-tools (was: ) > Validate scenario dmn import validation > --------------------------------------- > > Key: DROOLS-3422 > URL: https://issues.redhat.com/browse/DROOLS-3422 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Toni Rikkola > Priority: Minor > Labels: drools-tools > > When importing a dmn-scenario, validate the dmn file path it points to, and eventually discard import. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 December 2019