January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2209) Error with accumulator and DataSource being used in rule units

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-2209: ----------------------------------- Summary: Error with accumulator and DataSource being used in rule units Key: DROOLS-2209 URL: https://issues.jboss.org/browse/DROOLS-2209 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3488) Add support for custom syslog message formatting

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3488?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-3488: --------------------------------------- This is something that's been planned, but we'd want to change all the attributes at once. The blocking issue is support for TLS connections. This is something that's being worked on though. > Add support for custom syslog message formatting > ------------------------------------------------ > > Key: WFCORE-3488 > URL: https://issues.jboss.org/browse/WFCORE-3488 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Reporter: Rene Böing > Assignee: James Perkins > > Hello, > it would be great, if the syslog logging handler would be able to use a custom message formatter, just like the other logging handlers do. This would be much appreciated, since i wouldn't need to implement my own logic to append for example a stacktrace to a message. > Kind regards, > Rene -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3488) Add support for custom syslog message formatting

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3488?page=com.atlassian.jira.plugi... ] James Perkins closed WFCORE-3488. --------------------------------- Resolution: Duplicate Issue > Add support for custom syslog message formatting > ------------------------------------------------ > > Key: WFCORE-3488 > URL: https://issues.jboss.org/browse/WFCORE-3488 > Project: WildFly Core > Issue Type: Enhancement > Components: Logging > Reporter: Rene Böing > Assignee: James Perkins > > Hello, > it would be great, if the syslog logging handler would be able to use a custom message formatter, just like the other logging handlers do. This would be much appreciated, since i wouldn't need to implement my own logic to append for example a stacktrace to a message. > Kind regards, > Rene -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2189) Business central shows redundant warning messages from validation.

by Toni Rikkola (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2189?page=com.atlassian.jira.plugi... ] Toni Rikkola closed DROOLS-2189. -------------------------------- Resolution: Done > Business central shows redundant warning messages from validation. > ------------------------------------------------------------------ > > Key: DROOLS-2189 > URL: https://issues.jboss.org/browse/DROOLS-2189 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1165) Syntax error on Java EE for 6.4.0.Final (6.3.0.Final worked fine)

by Tanmay Kumar Pandey (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1165?page=com.atlassian.jira.plugi... ] Tanmay Kumar Pandey commented on DROOLS-1165: --------------------------------------------- I even tried upgrading to drools 7.5, I get same error regardless. Three errors are Error: unable to resolve method using strict-mode: and text=Unable to Analyse Expression log.debug > Syntax error on Java EE for 6.4.0.Final (6.3.0.Final worked fine) > ----------------------------------------------------------------- > > Key: DROOLS-1165 > URL: https://issues.jboss.org/browse/DROOLS-1165 > Project: Drools > Issue Type: Bug > Affects Versions: 6.4.0.Final > Environment: Java EE 7, Wildfly > Reporter: Matteo Mortari > Assignee: Mario Fusco > Priority: Minor > Attachments: 20160505.syntaxerroronjavaeefor640f.zip > > > Hello, not sure if this is actually a Drools issue, or just some compiler error due to some other dependencies issue. Anyhow attached reproducer contains a DRL syntactically correct, parses correctly 6.4.0.Final when not on Java EE. When on Java EE instead, fails to parse lamenting syntax error, snippet: > {code} > [ function valueSizeGEofvalueSizeGEof (line:42): Syntax error, static imports are only available if source level is 1.5 or greater > valueSizeGEof (line:42): The import java.util.stream.Collectors.groupingBy cannot be resolved > valueSizeGEof (line:44): Syntax error, static imports are only available if source level is 1.5 or greater > valueSizeGEof (line:44): The import com.acme.testaccumulatestreamonjavaee.MapOfList.mapOfList cannot be resolved > valueSizeGEof (line:46): Syntax error, static imports are only available if source level is 1.5 or greater > valueSizeGEof (line:46): The import com.acme.testaccumulatestreamonjavaee.EntryKey.entryKey cannot be resolved > valueSizeGEof (line:52): Syntax error, parameterized types are only available if source level is 1.5 or greater > valueSizeGEof (line:53): Type mismatch: cannot convert from Integer to int > valueSizeGEof (line:54): Syntax error, parameterized types are only available if source level is 1.5 or greater > valueSizeGEof (line:55): Syntax error, annotations are only available if source level is 1.5 or greater > valueSizeGEof (line:56): Syntax error, parameterized types are only available if source level is 1.5 or greater > ] > {code} > Please notice if using 6.3.0.Final, on Java EE, is OK without errors. > For the reproducer, maven {{clean test}} using profile {{wildfy82-embedded}}. I am using Arquillian to demonstrate the difference using version 6.3.0.Final Vs 6.4.0.Final. > Can you kindly advise, please? > Thank you > Ciao > MM -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1165) Syntax error on Java EE for 6.4.0.Final (6.3.0.Final worked fine)

by Tanmay Kumar Pandey (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1165?page=com.atlassian.jira.plugi... ] Tanmay Kumar Pandey edited comment on DROOLS-1165 at 1/3/18 10:31 AM: ---------------------------------------------------------------------- I even tried upgrading to drools 7.5, I get same error regardless. Three errors are Error: unable to resolve method using strict-mode: and text=Unable to Analyse Expression log.debug and Syntax error, static imports are only available if source level is 1.5 or greater was (Author: tkpandey001): I even tried upgrading to drools 7.5, I get same error regardless. Three errors are Error: unable to resolve method using strict-mode: and text=Unable to Analyse Expression log.debug > Syntax error on Java EE for 6.4.0.Final (6.3.0.Final worked fine) > ----------------------------------------------------------------- > > Key: DROOLS-1165 > URL: https://issues.jboss.org/browse/DROOLS-1165 > Project: Drools > Issue Type: Bug > Affects Versions: 6.4.0.Final > Environment: Java EE 7, Wildfly > Reporter: Matteo Mortari > Assignee: Mario Fusco > Priority: Minor > Attachments: 20160505.syntaxerroronjavaeefor640f.zip > > > Hello, not sure if this is actually a Drools issue, or just some compiler error due to some other dependencies issue. Anyhow attached reproducer contains a DRL syntactically correct, parses correctly 6.4.0.Final when not on Java EE. When on Java EE instead, fails to parse lamenting syntax error, snippet: > {code} > [ function valueSizeGEofvalueSizeGEof (line:42): Syntax error, static imports are only available if source level is 1.5 or greater > valueSizeGEof (line:42): The import java.util.stream.Collectors.groupingBy cannot be resolved > valueSizeGEof (line:44): Syntax error, static imports are only available if source level is 1.5 or greater > valueSizeGEof (line:44): The import com.acme.testaccumulatestreamonjavaee.MapOfList.mapOfList cannot be resolved > valueSizeGEof (line:46): Syntax error, static imports are only available if source level is 1.5 or greater > valueSizeGEof (line:46): The import com.acme.testaccumulatestreamonjavaee.EntryKey.entryKey cannot be resolved > valueSizeGEof (line:52): Syntax error, parameterized types are only available if source level is 1.5 or greater > valueSizeGEof (line:53): Type mismatch: cannot convert from Integer to int > valueSizeGEof (line:54): Syntax error, parameterized types are only available if source level is 1.5 or greater > valueSizeGEof (line:55): Syntax error, annotations are only available if source level is 1.5 or greater > valueSizeGEof (line:56): Syntax error, parameterized types are only available if source level is 1.5 or greater > ] > {code} > Please notice if using 6.3.0.Final, on Java EE, is OK without errors. > For the reproducer, maven {{clean test}} using profile {{wildfy82-embedded}}. I am using Arquillian to demonstrate the difference using version 6.3.0.Final Vs 6.4.0.Final. > Can you kindly advise, please? > Thank you > Ciao > MM -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1165) Syntax error on Java EE for 6.4.0.Final (6.3.0.Final worked fine)

by Tanmay Kumar Pandey (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1165?page=com.atlassian.jira.plugi... ] Tanmay Kumar Pandey commented on DROOLS-1165: --------------------------------------------- Hi Mario, I'm getting the same errors while deploying rules on Wildfly 10.1.0 with JAVA EE 8. Drools version is 6.4 > Syntax error on Java EE for 6.4.0.Final (6.3.0.Final worked fine) > ----------------------------------------------------------------- > > Key: DROOLS-1165 > URL: https://issues.jboss.org/browse/DROOLS-1165 > Project: Drools > Issue Type: Bug > Affects Versions: 6.4.0.Final > Environment: Java EE 7, Wildfly > Reporter: Matteo Mortari > Assignee: Mario Fusco > Priority: Minor > Attachments: 20160505.syntaxerroronjavaeefor640f.zip > > > Hello, not sure if this is actually a Drools issue, or just some compiler error due to some other dependencies issue. Anyhow attached reproducer contains a DRL syntactically correct, parses correctly 6.4.0.Final when not on Java EE. When on Java EE instead, fails to parse lamenting syntax error, snippet: > {code} > [ function valueSizeGEofvalueSizeGEof (line:42): Syntax error, static imports are only available if source level is 1.5 or greater > valueSizeGEof (line:42): The import java.util.stream.Collectors.groupingBy cannot be resolved > valueSizeGEof (line:44): Syntax error, static imports are only available if source level is 1.5 or greater > valueSizeGEof (line:44): The import com.acme.testaccumulatestreamonjavaee.MapOfList.mapOfList cannot be resolved > valueSizeGEof (line:46): Syntax error, static imports are only available if source level is 1.5 or greater > valueSizeGEof (line:46): The import com.acme.testaccumulatestreamonjavaee.EntryKey.entryKey cannot be resolved > valueSizeGEof (line:52): Syntax error, parameterized types are only available if source level is 1.5 or greater > valueSizeGEof (line:53): Type mismatch: cannot convert from Integer to int > valueSizeGEof (line:54): Syntax error, parameterized types are only available if source level is 1.5 or greater > valueSizeGEof (line:55): Syntax error, annotations are only available if source level is 1.5 or greater > valueSizeGEof (line:56): Syntax error, parameterized types are only available if source level is 1.5 or greater > ] > {code} > Please notice if using 6.3.0.Final, on Java EE, is OK without errors. > For the reproducer, maven {{clean test}} using profile {{wildfy82-embedded}}. I am using Arquillian to demonstrate the difference using version 6.3.0.Final Vs 6.4.0.Final. > Can you kindly advise, please? > Thank you > Ciao > MM -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2208) Sometimes the agenda stops firing even if there are outstanding activations to be evaluated

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-2208: ----------------------------------- Summary: Sometimes the agenda stops firing even if there are outstanding activations to be evaluated Key: DROOLS-2208 URL: https://issues.jboss.org/browse/DROOLS-2208 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2207) Validation and Verification panel is missing

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2207?page=com.atlassian.jira.plugi... ] Michael Anstis reassigned DROOLS-2207: -------------------------------------- Assignee: Toni Rikkola (was: Michael Anstis) > Validation and Verification panel is missing > -------------------------------------------- > > Key: DROOLS-2207 > URL: https://issues.jboss.org/browse/DROOLS-2207 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.6.0.Final > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Critical > > The Validation and Verification panel is missing. The server log contains error [1], however looking into the workbench war, all v&v jars seems to be present. > [1] > ERROR [org.drools.workbench.services.verifier.plugin.backend.VerifierWebWorkerServlet] (default task-119) Failed to load verifier web worker. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2207) Validation and Verification panel is missing

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2207: ----------------------------------- Summary: Validation and Verification panel is missing Key: DROOLS-2207 URL: https://issues.jboss.org/browse/DROOLS-2207 Project: Drools Issue Type: Bug Components: Guided Decision Table Editor Affects Versions: 7.6.0.Final Reporter: Jozef Marko Assignee: Michael Anstis Priority: Critical The Validation and Verification panel is missing. The server log contains error [1], however looking into the workbench war, all v&v jars seems to be present. [1] ERROR [org.drools.workbench.services.verifier.plugin.backend.VerifierWebWorkerServlet] (default task-119) Failed to load verifier web worker. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 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 January 2018