February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3063) Renaming Packages with Guided Rules fails - Rules not moved to correct package

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3063?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-3063. ------------------------------- Resolution: Done This won't be done due to changed team focus on DMN and ScenarioSimulation assets. > Renaming Packages with Guided Rules fails - Rules not moved to correct package > ------------------------------------------------------------------------------ > > Key: DROOLS-3063 > URL: https://issues.jboss.org/browse/DROOLS-3063 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Affects Versions: 7.13.0.Final > Reporter: Dominik Sandjaja > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > Renaming a package in the Drools Workbench renames the package but the guided rules (with DSLs) within that package still have the old package declaration in the created source code. Since there is no way to change the package declaration in the rules manually, I consider this a bug. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-716) Guvnor/BRMS Joda DateTime == operator breaking Guided Rule UI

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-716?page=com.atlassian.jira.plugin... ] Jozef Marko closed DROOLS-716. ------------------------------ Resolution: Done This won't be done due to changed team focus on DMN and ScenarioSimulation assets. > Guvnor/BRMS Joda DateTime == operator breaking Guided Rule UI > ------------------------------------------------------------- > > Key: DROOLS-716 > URL: https://issues.jboss.org/browse/DROOLS-716 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Affects Versions: 6.2.0.CR4 > Reporter: Daniel Daniel > Assignee: Mark Proctor > Priority: Major > Labels: drools-tools > > I get the following error in the logs when I save: > {noformat} > 02:33:35,790 ERROR [org.kie.workbench.common.services.datamodel.backend.server.cache.LRUProjectDataModelOracleCache] (http-/0.0.0.0:8080-1) org.joda.time.format.ISODateTimeFormat and org.joda.time.format.ISODateTimeFormat$Constants disagree on InnerClasses attribute > 02:33:35,829 ERROR [org.kie.workbench.common.services.datamodel.backend.server.cache.LRUProjectDataModelOracleCache] (http-/0.0.0.0:8080-1) org.joda.time.format.DateTimeFormatterBuilder and org.joda.time.format.DateTimeFormatterBuilder$TimeZoneId disagree on InnerClasses attribute > {noformat} > My breaking rule is > {noformat} > rule "Test DateTime" > when > $testDayA : TestDay($uniqueIdA : uniqueId, $dayA : day, valid == true) > $testDayB : TestDay(uniqueId != $uniqueIdA, day == $dayA, valid == true) > then > $testDayA.setValid(false); > update($testDayA); > end > {noformat} > The day variable is > {noformat} > private DateTime day; > {noformat} > I can get the UI closing and opening if I remove 'day == $dayA'. That is the expression that breaks the UI. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-533) Score Cards: Model classes created declaratively are not visible in Guided Score Card

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-533?page=com.atlassian.jira.plugin... ] Jozef Marko closed DROOLS-533. ------------------------------ Resolution: Won't Do This won't be done due to changed team focus on DMN and ScenarioSimulation assets. > Score Cards: Model classes created declaratively are not visible in Guided Score Card > ------------------------------------------------------------------------------------- > > Key: DROOLS-533 > URL: https://issues.jboss.org/browse/DROOLS-533 > Project: Drools > Issue Type: Bug > Components: Guided Score Card Editor > Reporter: Gennadiy Kruglov > Assignee: Mark Proctor > Priority: Major > Labels: drools-tools > > Model classes created declaratively in Data Modeler are not visible in drop-down list "Facts" when creating Guided Score Card. Model classes will become visible only after import their using config tab. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-604) Problems in code generation and parsing when a method is called from Guided Rules Editor

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-604?page=com.atlassian.jira.plugin... ] Jozef Marko closed DROOLS-604. ------------------------------ Resolution: Won't Do This won't be done due to changed team focus on DMN and ScenarioSimulation assets. > Problems in code generation and parsing when a method is called from Guided Rules Editor > ---------------------------------------------------------------------------------------- > > Key: DROOLS-604 > URL: https://issues.jboss.org/browse/DROOLS-604 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Affects Versions: 6.1.0.Final, 6.2.0.Beta1, 6.2.0.Beta2, 6.2.0.Beta3 > Reporter: Abel Marrero Santos > Assignee: Michael Anstis > Priority: Critical > Labels: drools-tools > Attachments: model-base-0.0.1-SNAPSHOT.jar > > > I have found a problem in code generation when we use the feature "call a method on <variable>" from the Guided Rule Editor. An InvocationTargetException caused by a ClassCastException is thrown in RuleModelDRLPersistenceImpl.generateSetMethodCallsMethod method. > I have found other issues that I think are related and that I will try to mention in the comments. I can also provide you with the maven artifact that I'm using. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-445) Drools Workbench throw Unable to expand in guided rule with DSL

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-445?page=com.atlassian.jira.plugin... ] Jozef Marko closed DROOLS-445. ------------------------------ Resolution: Won't Do This won't be done due to changed team focus on DMN and ScenarioSimulation assets. > Drools Workbench throw Unable to expand in guided rule with DSL > --------------------------------------------------------------- > > Key: DROOLS-445 > URL: https://issues.jboss.org/browse/DROOLS-445 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Affects Versions: 6.0.1.Final > Environment: Linux Debian 64 > Tomcat 7.0.42 > java version "1.6.0_27" > OpenJDK Runtime Environment (IcedTea6 1.12.6) (6b27-1.12.6-1~deb7u1) > OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) > Reporter: Claudio D'Angelo > Assignee: Mark Proctor > Priority: Major > Labels: drools-tools, dsl, guided, workbench > > Hi, > In a project workbench I've defined a data model, a drl, a dsl and an guided rule with dsl. > In the guided rule with dsl the wizard (edit tab) work correctly but when I click "Validate" > [6] Unable to expand: Richiesta( tipo == "RIMBORSO") > [7] Unable to expand: Richiesta( condizione == "LOG") > [9] Unable to expand: System.out.println("OK"); > My DSL is: > [when] La richiesta e' di tipo "{tipo}"=Richiesta( tipo == "{tipo}") > [when] la condizione e' "{condizione}"=Richiesta( condizione == "{condizione}") > [when] e=and > [then] stampa = System.out.println("OK"); > I've seen with the source tab of guided rule the converted rule: > 1. | import it.test.modulistica.Richiesta; > 2. | > 3. | rule "bbb" > 4. | dialect "mvel" > 5. | when > 6. | Richiesta( tipo == "RIMBORSO") > 7. | Richiesta( condizione == "LOG") > 8. | then > 9. | System.out.println("OK"); > 10. | end > but I think that this is the converted rule. I think that the source must be: > import it.test.modulistica.Richiesta; > rule "bbb" > dialect "mvel" > when > La richiesta e' di tipo "RIMBORSO" > la condizione e' "LOG" > then > stampa > end -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-442) Defect(s) in DSL and Enumerations

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-442?page=com.atlassian.jira.plugin... ] Jozef Marko closed DROOLS-442. ------------------------------ Resolution: Won't Do This won't be done due to changed team focus on DMN and ScenarioSimulation assets. > Defect(s) in DSL and Enumerations > --------------------------------- > > Key: DROOLS-442 > URL: https://issues.jboss.org/browse/DROOLS-442 > Project: Drools > Issue Type: Bug > Components: DSLs Editor, Enumerations Editor > Affects Versions: 6.0.1.Final > Reporter: Stephen Johns > Assignee: Mark Proctor > Priority: Major > Labels: drools-tools > > The following works like you would think: > [when]xxx {l:ENUM:MyBean.l} {x:ENUM:MyBean.x} {y:ENUM:MyBean.y}=eval($sep.foo("any", "any", "{l}", "{x}", "{y}", "", "")) > Defect 1 > If you remove the spaces between the "} {" > [when]xxx {l:ENUM:MyBean.l}{x:ENUM:MyBean.x}{y:ENUM:MyBean.y}=eval($sep.foo("any", "any", "{l}", "{x}", "{y}", "", "")) > l = "" > x = "" > y = l + x + y > Defect 2 > Even in the first case, if the Enumeration returns a value that has space(s) in it (which maybe should not be allowed?) it will make for odd substitutions as well. > Note that I need spaces to be supported. > Defect 3 > Regardless of the date format specified the substitution always dd-MMM-yyyy > {startTime:DATE:"dd-MMM-yyyy HH:mm"} > {startTime:DATE:"dd-MMM-yyyy:HH:mm"} > {startTime:DATE:"dd-MMM-yyyy@HH:mm"} > {startTime:DATE:"HH:mm"} > all result in "25-Feb-2014" -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1899) DSL View for use in business rules assets does not scroll to the right

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-1899?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-1899. ------------------------------- Resolution: Won't Do This won't be done due to the changed team focus on DMN and ScenarioSimulation assets. > DSL View for use in business rules assets does not scroll to the right > ---------------------------------------------------------------------- > > Key: DROOLS-1899 > URL: https://issues.jboss.org/browse/DROOLS-1899 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor, Guided Template Editor > Affects Versions: 5.5.0.Final > Environment: Guvnor-5.3.0.Final > Reporter: Amana Juricic > Assignee: Mark Coble > Priority: Minor > Labels: drools-tools > Attachments: screenshot.png > > > I have created a set of DSL. The words end up being longer than the standard box that comes up when I try to use the DSL in a business rule assets. > See the attached screenshot. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10591) Missing documentation for org.wildfly.naming capability

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFLY-10591?page=com.atlassian.jira.plugin... ] Yeray Borges reassigned WFLY-10591: ----------------------------------- Assignee: Yeray Borges > Missing documentation for org.wildfly.naming capability > ------------------------------------------------------- > > Key: WFLY-10591 > URL: https://issues.jboss.org/browse/WFLY-10591 > Project: WildFly > Issue Type: Task > Components: Documentation, Naming > Reporter: Jeff Mesnil > Assignee: Yeray Borges > Priority: Major > > The org.wildfly.naming capability must be documented in https://github.com/wildfly/wildfly-capabilities -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1718) Accept hexadecimal values in rule LHS

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-1718?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-1718. ------------------------------- Resolution: Won't Do Won't be done due to changed team focus on DMN and ScenarioSimulation assets. > Accept hexadecimal values in rule LHS > ------------------------------------- > > Key: DROOLS-1718 > URL: https://issues.jboss.org/browse/DROOLS-1718 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Reporter: Uli Bubenheimer > Priority: Minor > Labels: drools-tools > > It is not possible to use a hexadecimal value in the LHS of a rule. > The manual says: "All standard Java numeric primitives are supported." As hexadecimal values are standard Java numeric primitives, this could be considered not just a new feature, but a bug (documentation bug at least). > I found this issue first mentioned in the referenced user forum post from 2006; sadly, the poster did not create a JIRA issue as suggested, or at least I could not find one. > Example: > rule "bla" > when > Value( tag == 0x00080060 ) // ERROR! > then > //something > end -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2049) Remove private void checkMarshallingUsingDsl method

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-2049?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-2049. ------------------------------- Resolution: Won't Do Won't be done due to changed focus on DMN and ScenarioSImulation assets > Remove private void checkMarshallingUsingDsl method > --------------------------------------------------- > > Key: DROOLS-2049 > URL: https://issues.jboss.org/browse/DROOLS-2049 > Project: Drools > Issue Type: Task > Components: DSLs Editor > Affects Versions: 7.3.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > > The [testclass|https://github.com/kiegroup/drools/blob/master/drools-workbench...] contains methods shown bellow. There is potential error in tests that expect checkMarshallingUsingDsl will behave differently from checkMarshalling. This checkMarshallingUsingDsl should be removed and tests which use it should be rewritten. > {code:java} > private void checkMarshalling(String expected, > RuleModel m) { > String drl = ruleModelPersistence.marshal(m); > assertNotNull(drl); > if (expected != null) { > assertEqualsIgnoreWhitespace(expected, > drl); > } > } > private void checkMarshallingUsingDsl(String expected, > RuleModel m) { > String drl = ruleModelPersistence.marshal(m); > assertNotNull(drl); > if (expected != null) { > assertEqualsIgnoreWhitespace(expected, > drl); > } > } > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 February 2019