October 2019 - jboss-jira - Jboss List Archives

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

by Michael Biarnes Kiefer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4698?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer updated DROOLS-4698: ------------------------------------------- Fix Version/s: 7.30.0.Final (was: 7.29.0.Final) > Adding "expression" type handling for Collection type propereties > ----------------------------------------------------------------- > > Key: DROOLS-4698 > URL: https://issues.jboss.org/browse/DROOLS-4698 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing, Test Scenarios Editor > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Fix For: 7.30.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4522) Adding "expression" type handling

by Michael Biarnes Kiefer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4522?page=com.atlassian.jira.plugi... ] Michael Biarnes Kiefer updated DROOLS-4522: ------------------------------------------- Fix Version/s: 7.30.0.Final (was: 7.29.0.Final) > Adding "expression" type handling > --------------------------------- > > Key: DROOLS-4522 > URL: https://issues.jboss.org/browse/DROOLS-4522 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Fix For: 7.30.0.Final > > Attachments: can-be-suspended-expression.webm > > > Basically, with the changes introduced in this PR, every complex type object in Scenario has an additional property ("expression") where it will be possible to add expression logic to the referred object (fact). At the moment, the changes involve only front-end side. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4704) [DMN Designer] Constraint Enumeration widget overlaps when re-opened

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4704?page=com.atlassian.jira.plugi... ] Michael Anstis reassigned DROOLS-4704: -------------------------------------- Assignee: Guilherme Gomes (was: Michael Anstis) > [DMN Designer] Constraint Enumeration widget overlaps when re-opened > --------------------------------------------------------------------- > > Key: DROOLS-4704 > URL: https://issues.jboss.org/browse/DROOLS-4704 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.28.0.Final > Reporter: Michael Anstis > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: corrected-enum.png, overlapping-enum-items.png > > > The {{DataTypeConstraintEnumeration}} content of the {{DataTypeConstraintModal}} overlaps content when re-opening an enumeration definition. If the User clicks on and dismissed the "Constraint type" drop-down the content of the {{DataTypeConstraintModal}} is corrected. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4704) [DMN Designer] Constraint Enumeration widget overlaps when re-opened

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4704?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-4704: ----------------------------------- Priority: Minor (was: Major) > [DMN Designer] Constraint Enumeration widget overlaps when re-opened > --------------------------------------------------------------------- > > Key: DROOLS-4704 > URL: https://issues.jboss.org/browse/DROOLS-4704 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.28.0.Final > Reporter: Michael Anstis > Assignee: Guilherme Gomes > Priority: Minor > Labels: drools-tools > Attachments: corrected-enum.png, overlapping-enum-items.png > > > The {{DataTypeConstraintEnumeration}} content of the {{DataTypeConstraintModal}} overlaps content when re-opening an enumeration definition. If the User clicks on and dismissed the "Constraint type" drop-down the content of the {{DataTypeConstraintModal}} is corrected. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4704) [DMN Designer] Constraint Enumeration widget overlaps when re-opened

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4704?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-4704: ----------------------------------- Attachment: overlapping-enum-items.png > [DMN Designer] Constraint Enumeration widget overlaps when re-opened > --------------------------------------------------------------------- > > Key: DROOLS-4704 > URL: https://issues.jboss.org/browse/DROOLS-4704 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.28.0.Final > Reporter: Michael Anstis > Assignee: Guilherme Gomes > Priority: Minor > Labels: drools-tools > Attachments: corrected-enum.png, overlapping-enum-items.png > > > The {{DataTypeConstraintEnumeration}} content of the {{DataTypeConstraintModal}} overlaps content when re-opening an enumeration definition. If the User clicks on and dismissed the "Constraint type" drop-down the content of the {{DataTypeConstraintModal}} is corrected. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4704) [DMN Designer] Constraint Enumeration widget overlaps when re-opened

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4704?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-4704: ----------------------------------- Attachment: corrected-enum.png > [DMN Designer] Constraint Enumeration widget overlaps when re-opened > --------------------------------------------------------------------- > > Key: DROOLS-4704 > URL: https://issues.jboss.org/browse/DROOLS-4704 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.28.0.Final > Reporter: Michael Anstis > Assignee: Guilherme Gomes > Priority: Minor > Labels: drools-tools > Attachments: corrected-enum.png, overlapping-enum-items.png > > > The {{DataTypeConstraintEnumeration}} content of the {{DataTypeConstraintModal}} overlaps content when re-opening an enumeration definition. If the User clicks on and dismissed the "Constraint type" drop-down the content of the {{DataTypeConstraintModal}} is corrected. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4704) [DMN Designer] Constraint Enumeration widget overlaps when re-opened

by Michael Anstis (Jira)

Michael Anstis created DROOLS-4704: -------------------------------------- Summary: [DMN Designer] Constraint Enumeration widget overlaps when re-opened Key: DROOLS-4704 URL: https://issues.jboss.org/browse/DROOLS-4704 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.28.0.Final Reporter: Michael Anstis Assignee: Michael Anstis The {{DataTypeConstraintEnumeration}} content of the {{DataTypeConstraintModal}} overlaps content when re-opening an enumeration definition. If the User clicks on and dismissed the "Constraint type" drop-down the content of the {{DataTypeConstraintModal}} is corrected. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4702) [DMN Designer] The search is not working in grids

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4702?page=com.atlassian.jira.plugi... ] Guilherme Gomes resolved DROOLS-4702. ------------------------------------- Resolution: Duplicate Issue We already have a JIRA opened for indexing the headers as we're indexing the cells. > [DMN Designer] The search is not working in grids > ------------------------------------------------- > > Key: DROOLS-4702 > URL: https://issues.jboss.org/browse/DROOLS-4702 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Daniel José dos Santos > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > The search is not working in expression grids. > [Source|https://github.com/kiegroup/kie-wb-common/pull/2973#discussion_r33...]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4669) Scanner is not using container ClassLoader

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4669?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-4669: ------------------------------------- I cannot reproduce the problem, it is working for me, see attached screenshot. Am I missing something? > Scanner is not using container ClassLoader > ------------------------------------------ > > Key: DROOLS-4669 > URL: https://issues.jboss.org/browse/DROOLS-4669 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.28.0.Final > Environment: Java 11, Java 8, Linux Debian > Reporter: Pavel Tavoda > Assignee: Mario Fusco > Priority: Major > Attachments: drools-sample.zip, screenshot-1.png > > > I had issue with standard Spring project. My configuration ended with following exception: > {code:java} > Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath > at org.drools.compiler.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:117) > {code} > Because of this I have to setup KieSession this way: > {code:java} > KieServices kieServices = KieServices.Factory.get(); > ReleaseId kieRelease = kieServices.newReleaseId("sk.f4s", "encounter-rule", "1.0.0-SNAPSHOT"); > KieContainer kieContainer = kieServices.newKieContainer(kieRelease, this.getClass().getClassLoader()); > kieSession = kieContainer.newStatelessKieSession(); > {code} > After this everything works fine. However I want to reload my kBase with scanner. I add following two lines: > {code:java} > kieScanner = kieServices.newKieScanner(kieContainer); > kieScanner.start(1000l); > {code} > After this following exception is raised: > {code} > Exception in thread "Timer-0" java.lang.RuntimeException: Unable to load dialect 'org.drools.compiler.rule.builder.dialect.java.JavaDialectConfiguration:java:org.drools.compiler.rule.builder.dialect.java.JavaDialectConfiguration' > at org.drools.compiler.builder.impl.KnowledgeBuilderConfigurationImpl.addDialect(KnowledgeBuilderConfigurationImpl.java:394) > at org.drools.compiler.builder.impl.KnowledgeBuilderConfigurationImpl.buildDialectConfigurationMap(KnowledgeBuilderConfigurationImpl.java:380) > at org.drools.compiler.builder.impl.KnowledgeBuilderConfigurationImpl.init(KnowledgeBuilderConfigurationImpl.java:235) > at org.drools.compiler.builder.impl.KnowledgeBuilderConfigurationImpl.init(KnowledgeBuilderConfigurationImpl.java:187) > at org.drools.compiler.builder.impl.KnowledgeBuilderConfigurationImpl.<init>(KnowledgeBuilderConfigurationImpl.java:155) > at org.drools.compiler.kie.builder.impl.AbstractKieProject.getBuilderConfiguration(AbstractKieProject.java:302) > at org.drools.compiler.kie.builder.impl.AbstractKieProject.createKnowledgeBuilder(AbstractKieProject.java:288) > at org.drools.compiler.kie.builder.impl.AbstractKieProject.buildKnowledgePackages(AbstractKieProject.java:213) > at org.drools.compiler.kie.builder.impl.AbstractKieProject.verify(AbstractKieProject.java:75) > at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildKieProject(KieBuilderImpl.java:271) > at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildKieModule(KieBuilderImpl.java:264) > at org.drools.compiler.kie.builder.impl.InternalKieModule.build(InternalKieModule.java:120) > at org.kie.scanner.KieRepositoryScannerImpl.updateKieModule(KieRepositoryScannerImpl.java:200) > at org.kie.scanner.KieRepositoryScannerImpl.internalUpdate(KieRepositoryScannerImpl.java:185) > at org.kie.scanner.KieRepositoryScannerImpl.internalUpdate(KieRepositoryScannerImpl.java:55) > at org.drools.compiler.kie.builder.impl.AbstractKieScanner.scanNow(AbstractKieScanner.java:147) > at org.drools.compiler.kie.builder.impl.AbstractKieScanner$ScanTask.run(AbstractKieScanner.java:127) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath > at org.drools.compiler.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:117) > at org.drools.compiler.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:78) > at org.drools.compiler.builder.impl.KnowledgeBuilderConfigurationImpl.addDialect(KnowledgeBuilderConfigurationImpl.java:390) > ... 18 more > {code} > I guess reason is that scanner is not using ClassLoader from KieContainer. Of course it will be better to fix reason why 'The Eclipse JDT Core jar is not in the classpath' is raised anyway because I'm using just standard Spring Web project with two Spring contexts (application and Web) what is very standard approach. Compiler IS awailable on classpath only Drools classloader doesn't see it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4669) Scanner is not using container ClassLoader

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4669?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-4669: -------------------------------- Attachment: screenshot-1.png > Scanner is not using container ClassLoader > ------------------------------------------ > > Key: DROOLS-4669 > URL: https://issues.jboss.org/browse/DROOLS-4669 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.28.0.Final > Environment: Java 11, Java 8, Linux Debian > Reporter: Pavel Tavoda > Assignee: Mario Fusco > Priority: Major > Attachments: drools-sample.zip, screenshot-1.png > > > I had issue with standard Spring project. My configuration ended with following exception: > {code:java} > Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath > at org.drools.compiler.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:117) > {code} > Because of this I have to setup KieSession this way: > {code:java} > KieServices kieServices = KieServices.Factory.get(); > ReleaseId kieRelease = kieServices.newReleaseId("sk.f4s", "encounter-rule", "1.0.0-SNAPSHOT"); > KieContainer kieContainer = kieServices.newKieContainer(kieRelease, this.getClass().getClassLoader()); > kieSession = kieContainer.newStatelessKieSession(); > {code} > After this everything works fine. However I want to reload my kBase with scanner. I add following two lines: > {code:java} > kieScanner = kieServices.newKieScanner(kieContainer); > kieScanner.start(1000l); > {code} > After this following exception is raised: > {code} > Exception in thread "Timer-0" java.lang.RuntimeException: Unable to load dialect 'org.drools.compiler.rule.builder.dialect.java.JavaDialectConfiguration:java:org.drools.compiler.rule.builder.dialect.java.JavaDialectConfiguration' > at org.drools.compiler.builder.impl.KnowledgeBuilderConfigurationImpl.addDialect(KnowledgeBuilderConfigurationImpl.java:394) > at org.drools.compiler.builder.impl.KnowledgeBuilderConfigurationImpl.buildDialectConfigurationMap(KnowledgeBuilderConfigurationImpl.java:380) > at org.drools.compiler.builder.impl.KnowledgeBuilderConfigurationImpl.init(KnowledgeBuilderConfigurationImpl.java:235) > at org.drools.compiler.builder.impl.KnowledgeBuilderConfigurationImpl.init(KnowledgeBuilderConfigurationImpl.java:187) > at org.drools.compiler.builder.impl.KnowledgeBuilderConfigurationImpl.<init>(KnowledgeBuilderConfigurationImpl.java:155) > at org.drools.compiler.kie.builder.impl.AbstractKieProject.getBuilderConfiguration(AbstractKieProject.java:302) > at org.drools.compiler.kie.builder.impl.AbstractKieProject.createKnowledgeBuilder(AbstractKieProject.java:288) > at org.drools.compiler.kie.builder.impl.AbstractKieProject.buildKnowledgePackages(AbstractKieProject.java:213) > at org.drools.compiler.kie.builder.impl.AbstractKieProject.verify(AbstractKieProject.java:75) > at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildKieProject(KieBuilderImpl.java:271) > at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildKieModule(KieBuilderImpl.java:264) > at org.drools.compiler.kie.builder.impl.InternalKieModule.build(InternalKieModule.java:120) > at org.kie.scanner.KieRepositoryScannerImpl.updateKieModule(KieRepositoryScannerImpl.java:200) > at org.kie.scanner.KieRepositoryScannerImpl.internalUpdate(KieRepositoryScannerImpl.java:185) > at org.kie.scanner.KieRepositoryScannerImpl.internalUpdate(KieRepositoryScannerImpl.java:55) > at org.drools.compiler.kie.builder.impl.AbstractKieScanner.scanNow(AbstractKieScanner.java:147) > at org.drools.compiler.kie.builder.impl.AbstractKieScanner$ScanTask.run(AbstractKieScanner.java:127) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > Caused by: java.lang.RuntimeException: The Eclipse JDT Core jar is not in the classpath > at org.drools.compiler.rule.builder.dialect.java.JavaDialectConfiguration.setCompiler(JavaDialectConfiguration.java:117) > at org.drools.compiler.rule.builder.dialect.java.JavaDialectConfiguration.init(JavaDialectConfiguration.java:78) > at org.drools.compiler.builder.impl.KnowledgeBuilderConfigurationImpl.addDialect(KnowledgeBuilderConfigurationImpl.java:390) > ... 18 more > {code} > I guess reason is that scanner is not using ClassLoader from KieContainer. Of course it will be better to fix reason why 'The Eclipse JDT Core jar is not in the classpath' is raised anyway because I'm using just standard Spring Web project with two Spring contexts (application and Web) what is very standard approach. Compiler IS awailable on classpath only Drools classloader doesn't see it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2019