[JBoss JIRA] (DROOLS-4575) Test Scenario: unsaved changes warning appears even if file has not been changed
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-4575?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-4575:
-----------------------------------
Sprint: 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2) (was: 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10))
> Test Scenario: unsaved changes warning appears even if file has not been changed
> --------------------------------------------------------------------------------
>
> Key: DROOLS-4575
> URL: https://issues.redhat.com/browse/DROOLS-4575
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Daniele Zonca
> Priority: Major
> Labels: CustomerFocus, drools-tools
>
> If user opens a scesim file and then close it, no confirmation message should be opened
> h2. Manual Acceptance Test
> - Opening and closing without changes
> - Open, change data in cell, close
> - Open, add column, remove column, change column binding, close
> - Open, Change settings on the settings panel (e.g. ruleflow group, kie session), close
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5059) Verifier: GDST columns empty enumeration should be ignored
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5059?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5059:
-----------------------------------
Sprint: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2) (was: 2020 Week 07-09 (from Feb 10))
> Verifier: GDST columns empty enumeration should be ignored
> ----------------------------------------------------------
>
> Key: DROOLS-5059
> URL: https://issues.redhat.com/browse/DROOLS-5059
> Project: Drools
> Issue Type: Bug
> Components: verifier
> Affects Versions: 7.33.0.Final
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Major
> Labels: drools-tools
>
> Not sure how the problem GDST is created, but it looks like there is a scenario where the value list for column is empty instead of null and the empty String as value list triggered the Verifier to think the column is an enumeration column.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-3002) Redo PMML scorecards rules to use executable model
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-3002?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-3002:
-----------------------------------
Sprint: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2) (was: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10))
> Redo PMML scorecards rules to use executable model
> --------------------------------------------------
>
> Key: DROOLS-3002
> URL: https://issues.redhat.com/browse/DROOLS-3002
> Project: Drools
> Issue Type: Enhancement
> Components: PMML
> Affects Versions: 7.12.0.Final
> Reporter: Lance Leverich
> Assignee: Gabriele Cardosi
> Priority: Major
> Labels: PMMLRefactor, drools-core
>
> Re-factoring of the classes and mechanisms that generate rules and classes from a PMML resource that contains a Scorecard model.
> # Make further usage of POJOs to replace any types declared within the rule file
> # Change the rules generated so that the rules are Java, based on the executable model
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-2845) Extend the existing verifier to support DMN tables
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-2845?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-2845:
-----------------------------------
Sprint: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2) (was: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10))
> Extend the existing verifier to support DMN tables
> --------------------------------------------------
>
> Key: DROOLS-2845
> URL: https://issues.redhat.com/browse/DROOLS-2845
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor, verifier
> Reporter: Toni Rikkola
> Assignee: Toni Rikkola
> Priority: Optional
> Labels: UX, drools-tools, verifier
>
> h1. Goal
> Reuse the V&V created for Guided Decision Tables on the DMN tables.
> h1. Workload divided to steps
> I propose the work goes in the following steps. After each step I should be able to merge into master.
> Steps:
> # Move Verifier core to kie-wb-common
> # Move V&V reporting UI to kie-wb-common
> # Make the web worker connector reusable for different V&V types
> # -Make a servlet module for DMN that allows the download of the Web Worker.-
> # Create an adapter for DMN tables
> # Add support for ranges ( these are given in DMN so no need to use JSR303 )
> # Duplicate i18n of the V&V for DMN or unify the reports so that the terms make sense
> The workload has changed. Now the goal is to reuse the DRL V&V codes in the existing DMN Codes. This means most of the work done for this ticket has no effect and the goal is to adjust to existing DMN V&V reporting, not the other way around.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5067) Bound property check mark
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-5067?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-5067:
-----------------------------------
Sprint: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2) (was: 2020 Week 07-09 (from Feb 10))
> Bound property check mark
> -------------------------
>
> Key: DROOLS-5067
> URL: https://issues.redhat.com/browse/DROOLS-5067
> Project: Drools
> Issue Type: Enhancement
> Components: Scenario Simulation and Testing
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Trivial
> Labels: drools-tools
> Attachments: ExpressionTick.webm
>
>
> In Test Scenario we have a feature for highlighting a property during binding to a fact property. However we do not highlight the already bound fact property.
> In other words, if a column is bound to some fact property, there should be check mark in test tools panel next to the given fact property.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-4895) Backport RuleUnitComponentFactory#createRuleUnitDescription( KiePackage, String );
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-4895?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-4895:
-----------------------------------
Sprint: 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2) (was: 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10))
> Backport RuleUnitComponentFactory#createRuleUnitDescription( KiePackage, String );
> ----------------------------------------------------------------------------------
>
> Key: DROOLS-4895
> URL: https://issues.redhat.com/browse/DROOLS-4895
> Project: Drools
> Issue Type: Bug
> Reporter: Edoardo Vacchi
> Assignee: Edoardo Vacchi
> Priority: Major
> Labels: drools-core
>
> add {{RuleUnitDescription createRuleUnitDescription( KiePackage pkg, String ruleUnitSimpleName );}} it should be a no-op because it is only used in Kogito
> also {{RuleUnitDescriptionLoader}} may use this method in case {{createRuleUnitDescription( KiePackage pkg, Class<?> ruleUnit );} fails. However, this cannot happen in Drools 7, as the RuleUnit is always described by a Class, so it will always return null (it's a no-op after all). Reasons for backport are only code alignment.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-3879) Create Kogito version of Test Scenarios designer
by Kris Verlaenen (Jira)
[ https://issues.redhat.com/browse/DROOLS-3879?page=com.atlassian.jira.plug... ]
Kris Verlaenen updated DROOLS-3879:
-----------------------------------
Sprint: 2019 Week 41-43 (from Okt 7), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2) (was: 2019 Week 41-43 (from Okt 7), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30), 2020 Week 04-06 (from Jan 20), 2020 Week 07-09 (from Feb 10))
> 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: Yeser Amer
> Priority: Major
> Labels: drools-tools
>
> Scope of this PR is to create a *Kogito/client-side only* versions of scesim editor.
> From an architectural point of view, the actual implementation has been moved (in the past) inside a common module: `drools-wb-scenario-simulation-editor-client`.
> Access to it has been "hided" behind a wrapper interface with three actual implementations:
> * `drools-wb-scenario-simulation-editor-businesscentral-client` for BusinessCentral environment
> * `drools-wb-scenario-simulation-editor-kogito-testing` to provide a development/debugging setup for the *Kogito/client-side only* environment
> * `drools-wb-scenario-simulation-editor-kogito-runtime` that should be the one deployed in actual client-side only containers (e.g. VSCode).
> As agreed upon in the last summer (https://issues.redhat.com/browse/AF-2041), the kogito editors should depend upon a common library, `org.kie.workbench:kie-wb-common-kogito-webapp-base` to put all the code/maven configuration shared by the different editors in one single place.
> Currently, only the two kogito-related scesim modules fulfill that requirement; all other editors, starting from DMN, should be adapted to this approach.
> Kogito-testing module is a standalone showcase that provides some minimum interaction to:
> * load DMN files
> * create DMN-related scesim assets, selecting one of the imported DMN.
> Currently - RULE/data object model scesim is disabled.
> Kogito-runtime module is the version that should run purely client side. It does not provide any graphical widget to load/create/save asset.
> Some minimal tests may be done in the following way:
> # full compilation (i.e. included GWT compilation) of the runtime module
> # open the `drools-wb/drools-wb-screens/drools-wb-scenario-simulation-editor/drools-wb-scenario-simulation-editor-kogito-runtime/target/drools-wb-scenario-simulation-editor-kogito-runtime/index.html` file inside Chrome
> # inside the Chrome dev console, issue the command `window.gwtEditorBeans.get("ScenarioSimulationEditorKogitoRuntimeScreen").get().setContent("")`; this will show the "New Scesim" popup, where user may choose to create a DMN or RULE scesim; of course, inside Chrome it is not possible to have a reference to other resources, so only "Rule" will work; at the same time, no Data model is available inside Chrome, so the right panel will be empty and the only expected result is an empty grid.
> # edit the asset
> # invoke window.gwtEditorBeans.get("ScenarioSimulationEditorKogitoRuntimeScreen").get().getContent() and store the returned xml
> # invoke window.gwtEditorBeans.get("ScenarioSimulationEditorKogitoRuntimeScreen").get().setContent method with the stored xml
> Some tricks: to avoid CORS and other policy-related issues:
> # set chrome://flags/#allow-insecure-localhost for invalid certificates error
> # start chrome from cli with the command `chrome --allow-file-access-from-files` to allow loading from file.
> /----/
> The "run scenario" functionality won't be implemented by this PR.
> All the functionalities related to file system/resource access will be simulated in the testing modules (but only for the DMN models), and for the runtime module will depend on the API/environment provided by VSCode
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13074) application context is enabled to mod_cluster for servers that are started as suspended in the JBoss EAP 7.2
by Chao Wang (Jira)
[ https://issues.redhat.com/browse/WFLY-13074?page=com.atlassian.jira.plugi... ]
Chao Wang updated WFLY-13074:
-----------------------------
Labels: downstream_dependency (was: )
> application context is enabled to mod_cluster for servers that are started as suspended in the JBoss EAP 7.2
> ------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-13074
> URL: https://issues.redhat.com/browse/WFLY-13074
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster, Web (Undertow)
> Affects Versions: 19.0.0.Beta1
> Reporter: Chao Wang
> Assignee: Chao Wang
> Priority: Major
> Labels: downstream_dependency
>
> When a server that is running is suspended, the application contexts are stopped:
> {code:java}
> 2020-01-31 09:27:47,548 DEBUG [org.jboss.modcluster] (ServerService Thread Pool -- 6) MODCLUSTER000008: Received stop context event for default-host:/appname
> 2020-01-31 09:27:47,548 DEBUG [org.jboss.modcluster] (ServerService Thread Pool -- 6) MODCLUSTER000010: Sending DISABLE-APP for default-host:/appname
> 2020-01-31 09:27:47,550 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 6) MODCLUSTER000021: All pending requests drained from default-host:/appname in 0.0 seconds
> {code}
> From undertow loadbalancer:
> {code:java}
> 2020-01-31 09:24:55,828 DEBUG [io.undertow] (default task-1) UT005057: Sending MCMP response to destination: /127.0.0.1:44386, HTTP status: 200, Headers: {Content-Type=[text/plain; charset=ISO-8859-1]}, response: Type=STOP-APP-RSP,JvmRoute=slave:server1Alias=default-host,localhostContext=/appnameRequests=0
> {code}
> But if a server is started as suspended, the contexts are enabled:
> {code:java}
> 2020-01-31 09:34:10,570 DEBUG [org.jboss.modcluster] (ServerService Thread Pool -- 81) MODCLUSTER000005: Received add context event for default-host:/appname
> 2020-01-31 09:34:10,570 DEBUG [org.jboss.modcluster] (ServerService Thread Pool -- 81) MODCLUSTER000007: Received start context event for default-host:/appname
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months