August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4403) Scenario Simulation: Export DMN/Rule runner logs

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4403?page=com.atlassian.jira.plugi... ] Gabriele Cardosi updated DROOLS-4403: ------------------------------------- Story Points: 1 (was: 5) > Scenario Simulation: Export DMN/Rule runner logs > ------------------------------------------------ > > Key: DROOLS-4403 > URL: https://issues.jboss.org/browse/DROOLS-4403 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation, ScenarioSimulationTeam > > Export runner information for DMN/Rule-scesim -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4602) Add support for DigestPasswordMapper to JDBC SecurityRealm

by Darran Lofthouse (Jira)

Darran Lofthouse created WFCORE-4602: ---------------------------------------- Summary: Add support for DigestPasswordMapper to JDBC SecurityRealm Key: WFCORE-4602 URL: https://issues.jboss.org/browse/WFCORE-4602 Project: WildFly Core Issue Type: Feature Request Components: Security Reporter: Darran Lofthouse Fix For: 11.0.0.Beta1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4245) [DMN Designer] Documentation - Enhance presentation

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-4245?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-4245: --------------------------------------- [~bdellasc] I like the "supported by Red Hat" logo, and I think we are close now. The remaining concerns are: * the most important information on that page is the model name "Loan Comparison", but the items "in the spotlight" are a KIE logo and a generic "DMN Model Documentation". Can we remove the "DMN Model Documentation" title completely, and give emphasis to the "Loan Comparison" model name? * I am not sure if we should be using the KIE logo or the Drools logo. Thoughts? Since this is a DMN report I am inclined to favour the Drools logo, but I could be convinced otherwise. > [DMN Designer] Documentation - Enhance presentation > --------------------------------------------------- > > Key: DROOLS-4245 > URL: https://issues.jboss.org/browse/DROOLS-4245 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Brian Dellascio > Priority: Major > Labels: UX, UXTeam, VisualDesign, drools-tools > Attachments: RedHat_KIE_logo.eps, RedHat_KIE_logo.png, RedHat_KIE_logo.svg, doc.pdf, new_doc.pdf > > > Enhance styles and presentation of the Documentation output. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4429) Port 4375 to Kogito

by Luca Molteni (Jira)

Luca Molteni created DROOLS-4429: ------------------------------------ Summary: Port 4375 to Kogito Key: DROOLS-4429 URL: https://issues.jboss.org/browse/DROOLS-4429 Project: Drools Issue Type: Task Reporter: Luca Molteni Assignee: Luca Molteni -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4427) Port DROOLS-4374 to Kogito

by Luca Molteni (Jira)

Luca Molteni created DROOLS-4427: ------------------------------------ Summary: Port DROOLS-4374 to Kogito Key: DROOLS-4427 URL: https://issues.jboss.org/browse/DROOLS-4427 Project: Drools Issue Type: Task Reporter: Luca Molteni Assignee: Luca Molteni -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4428) Port DROOLS-4188 to Kogito

by Luca Molteni (Jira)

Luca Molteni created DROOLS-4428: ------------------------------------ Summary: Port DROOLS-4188 to Kogito Key: DROOLS-4428 URL: https://issues.jboss.org/browse/DROOLS-4428 Project: Drools Issue Type: Task Reporter: Luca Molteni Assignee: Luca Molteni -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4307) Drools unable to compile rules when using a declared enum in the DRL file

by Luca Molteni (Jira)

[ https://issues.jboss.org/browse/DROOLS-4307?page=com.atlassian.jira.plugi... ] Luca Molteni resolved DROOLS-4307. ---------------------------------- Resolution: Done > Drools unable to compile rules when using a declared enum in the DRL file > ------------------------------------------------------------------------- > > Key: DROOLS-4307 > URL: https://issues.jboss.org/browse/DROOLS-4307 > Project: Drools > Issue Type: Bug > Reporter: Robert Buchmann > Assignee: Luca Molteni > Priority: Major > Attachments: drl.zip > > > I am finding inconsistent behaviour between drools reading rules from a local file (as a fileSystemResource) as opposed to pre compiling the rules into a kjar. > This happens if I use an enum declared within the drl file in the "when" or "then" section of a rule within the same drl file. > The rule runs perfectly as expected if I load the rule from the filesystem, but fails to run if I have pre-compiled the rule. For this reason I think this is a bug as I would expect the same behaviour for both ways of running rules. > I outlined the problem in more detail stackoverflow: > https://stackoverflow.com/questions/56989080/drools-maven-plugin-not-unde... > This is running JAVA8 and drools 7.23.0.Final -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4307) Drools unable to compile rules when using a declared enum in the DRL file

by Luca Molteni (Jira)

[ https://issues.jboss.org/browse/DROOLS-4307?page=com.atlassian.jira.plugi... ] Luca Molteni reopened DROOLS-4307: ---------------------------------- > Drools unable to compile rules when using a declared enum in the DRL file > ------------------------------------------------------------------------- > > Key: DROOLS-4307 > URL: https://issues.jboss.org/browse/DROOLS-4307 > Project: Drools > Issue Type: Bug > Reporter: Robert Buchmann > Assignee: Luca Molteni > Priority: Major > Attachments: drl.zip > > > I am finding inconsistent behaviour between drools reading rules from a local file (as a fileSystemResource) as opposed to pre compiling the rules into a kjar. > This happens if I use an enum declared within the drl file in the "when" or "then" section of a rule within the same drl file. > The rule runs perfectly as expected if I load the rule from the filesystem, but fails to run if I have pre-compiled the rule. For this reason I think this is a bug as I would expect the same behaviour for both ways of running rules. > I outlined the problem in more detail stackoverflow: > https://stackoverflow.com/questions/56989080/drools-maven-plugin-not-unde... > This is running JAVA8 and drools 7.23.0.Final -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12280) DatabaseTimerPersistence does not detect mssql driver type

by Filippe Spolti (Jira)

[ https://issues.jboss.org/browse/WFLY-12280?page=com.atlassian.jira.plugin... ] Filippe Spolti updated WFLY-12280: ---------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/12494, https://github.com/wildfly/wildfly/pull/12495 (was: https://github.com/wildfly/wildfly/pull/12494) > DatabaseTimerPersistence does not detect mssql driver type > ---------------------------------------------------------- > > Key: WFLY-12280 > URL: https://issues.jboss.org/browse/WFLY-12280 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 17.0.1.Final > Reporter: David Ward > Assignee: Filippe Spolti > Priority: Major > Fix For: 18.0.0.Beta1 > > > The DatabaseTimerPersistence class' identifyDialect method [1] only recognizes the "microsoft" driver when it should also recognize the "mssql" driver, similar to how the code checks for both "hsql" and "hypersonic". > The result of this is that instead of the "create-table.mysql" property being loaded from timer-sql.properties [2], the default "create-table" property is used. > The repercussion of _that_ is that the TIMESTAMP column type is used instead of the DATETIME2 column type when creating the table, which results in the error "WFLYEJB0163: Cannot create table for timer persistence: com.microsoft.sqlserver.jdbc.SQLServerException: A table can only have one timestamp column. Because table 'JBOSS_EJB_TIMER' already has one, the column 'NEXT_DATE' cannot be added." Similar reports can be found all over the internet, for example, here: [3] > We ran into this problem when trying to fix RHPAM-2002. Please read the comments from this point forward: [4] > I _think_ the fix would be as simple as changing this line: > {code:java} > }else if (name.toLowerCase().contains("microsoft")) { > {code} > to this: > {code:java} > }else if (name.toLowerCase().contains("mssql") || name.toLowerCase().contains("microsoft")) { > {code} > [1] https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jbo... > [2] https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main/reso... > [3] https://stackoverflow.com/questions/12063850/multiple-timestamp-columns-i... > [4] https://issues.jboss.org/browse/RHPAM-2002?focusedCommentId=13757468&page... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4599) Default AuthenticationContext is a static with undefined behaviour

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFCORE-4599?page=com.atlassian.jira.plugi... ] Darran Lofthouse reassigned WFCORE-4599: ---------------------------------------- Assignee: Stuart Douglas (was: Darran Lofthouse) > Default AuthenticationContext is a static with undefined behaviour > ------------------------------------------------------------------ > > Key: WFCORE-4599 > URL: https://issues.jboss.org/browse/WFCORE-4599 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Priority: Major > Fix For: 10.0.0.Beta4 > > > The default AuthenticationContext global supplier initializes a static based on wildfly-config..xml found in the current class loader. > As this is initialised lazily the result of this will depend on which deployment is used to access this first. If there are multiple deployments other deployments can end up using the wrong configuration. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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 August 2019