March 2020 - jboss-jira - Jboss List Archives

[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)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5057) Align gwt jsonix versions

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5057?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5057: ----------------------------------- Sprint: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2) (was: 2020 Week 07-09 (from Feb 10)) > Align gwt jsonix versions > ------------------------- > > Key: DROOLS-5057 > URL: https://issues.redhat.com/browse/DROOLS-5057 > Project: Drools > Issue Type: Task > Affects Versions: 7.34.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Minor > Labels: drools-tools, kogito-tooling > > Found during DROOLS-4249 review. > We should align gwt jsonix versions used by DMN and SCESIM kogito marshallers. > For more details see https://github.com/kiegroup/drools-wb/pull/1306#discussion_r378209786 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[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)

4 years, 2 months

1
0
0 / 0

[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)

4 years, 2 months

1
0
0 / 0

[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)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5050) Issue with alpha node and expired events rule execution

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5050?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-5050: --------------------------------- Sprint: 2020 Week 10-12 (from Mar 2) (was: 2020 Week 07-09 (from Feb 10)) > Issue with alpha node and expired events rule execution > ------------------------------------------------------- > > Key: DROOLS-5050 > URL: https://issues.redhat.com/browse/DROOLS-5050 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.33.0.Final > Reporter: Marcell Pessanha Cruz > Assignee: Luca Molteni > Priority: Critical > > Alpha node based rules evaluated for expired events are not all executed during the inference cycle. > With the following rules: > {noformat} > declare DummyEvent > @role( event ) > @timestamp( eventTimestamp ) > @expires( 1s ) > end > rule R1 > when > $evt : DummyEvent() > then > end > rule R2 > when > $evt : ApplicationEvent() > then > end > {noformat} > and this code to execute: > {noformat} > public interface ApplicationEvent { } > public static class DummyEvent implements ApplicationEvent {...} > /* .... */ > final KieSession kieSession = kieBase.newKieSession( sessionConfig, null ); > PseudoClockScheduler clock = kieSession.getSessionClock(); > final long currentTime = clock.getCurrentTime(); > clock.advanceTime(10, TimeUnit.SECONDS); > kieSession.insert(new DummyEvent(10, currentTime)); > kieSession.fireAllRules() > {noformat} > then only the *R1* rule is executed, not R2. > Note: the same test case passes on 7.2.0.Final and earlier versions. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4891) Further Optimize Lambdas in Executable Model

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-4891?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-4891: --------------------------------- Sprint: 2020 Week 10-12 (from Mar 2) (was: 2020 Week 07-09 (from Feb 10)) > Further Optimize Lambdas in Executable Model > -------------------------------------------- > > Key: DROOLS-4891 > URL: https://issues.redhat.com/browse/DROOLS-4891 > Project: Drools > Issue Type: Enhancement > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > Labels: good-first-issue > > Lambda shouldn't be externalized depending on the variable name but on the actual lambda. > So > person.name == a > person.name == b > Is effectively the same lambda and should externalized once. > Hint: we could rename the parameters to p1, p2, p3, promote the types to fully qualified names and get this result. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5063) Experimenting with type safe DMN evaluation

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5063?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-5063: --------------------------------- Sprint: 2020 Week 10-12 (from Mar 2) (was: 2020 Week 07-09 (from Feb 10)) > Experimenting with type safe DMN evaluation > ------------------------------------------- > > Key: DROOLS-5063 > URL: https://issues.redhat.com/browse/DROOLS-5063 > Project: Drools > Issue Type: Enhancement > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5025) Wrong BitMask created by a complex setter argument in modify block

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5025?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-5025: --------------------------------- Sprint: 2020 Week 10-12 (from Mar 2) (was: 2020 Week 07-09 (from Feb 10)) > Wrong BitMask created by a complex setter argument in modify block > ------------------------------------------------------------------ > > Key: DROOLS-5025 > URL: https://issues.redhat.com/browse/DROOLS-5025 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.32.0.Final > Reporter: Toshiya Kobayashi > Assignee: Luca Molteni > Priority: Major > Labels: good-first-issue > > With a complex setter argument in modify block like this: > {noformat} > import org.drools.modelcompiler.domain.Person; > rule R > when > $p: Person(address.street == "street1") > then > modify($p) { setLikes( String.valueOf(($p.getAddress().getStreet() + $p.getAddress().getCity()))) }; > end > {noformat} > executable model creates BitMask for "likes" and "address" thus causes a wrong property reactivity behavior. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4984) Enable the executable model in Optaplanner

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-4984?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-4984: --------------------------------- Sprint: 2020 Week 10-12 (from Mar 2) (was: 2020 Week 07-09 (from Feb 10)) > Enable the executable model in Optaplanner > ------------------------------------------ > > Key: DROOLS-4984 > URL: https://issues.redhat.com/browse/DROOLS-4984 > Project: Drools > Issue Type: Bug > Components: executable model > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > > Currently it's disabled -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2020