March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11908) Subsystem namespace versions are out of date in appclient.xml

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11908?page=com.atlassian.jira.plugin... ] Brian Stansberry moved JBEAP-16611 to WFLY-11908: ------------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-11908 (was: JBEAP-16611) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Application Client (was: Application Client) Affects Version/s: 16.0.0.Final (was: 7.2.0.GA) > Subsystem namespace versions are out of date in appclient.xml > ------------------------------------------------------------- > > Key: WFLY-11908 > URL: https://issues.jboss.org/browse/WFLY-11908 > Project: WildFly > Issue Type: Bug > Components: Application Client > Affects Versions: 16.0.0.Final > Reporter: Debbie Steigner > Assignee: Brian Stansberry > Priority: Minor > > The default Datasources namespace version for the other configurations (standalone.xml, domain.xml) is 5, but is set to version 2 in the appclient.xml -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3794) Inconsistent null check between JITed and non-JITed "contains"/"memberOf" condition

by Max Zerzouri (Jira)

Max Zerzouri created DROOLS-3794: ------------------------------------ Summary: Inconsistent null check between JITed and non-JITed "contains"/"memberOf" condition Key: DROOLS-3794 URL: https://issues.jboss.org/browse/DROOLS-3794 Project: Drools Issue Type: Bug Affects Versions: 7.19.0.Final Reporter: Max Zerzouri Assignee: Mario Fusco Attachments: DroolsTest.java, drl.drl A condition such as {{list contains item}} or {{item memberOf list}} seems to correspond to {{EvaluatorHelper.contains(list, item)}}, but when this has been compiled through {{ASMConditionEvaluatorJitter}}, the condition includes the additional constraint, {{item != null}}. This differs to the non-JITed condition, which does not require {{item}} to be non-null. Attached an example {{.drl}} file as an example case, and a simple runner. Running {{java DroolsTest 14}} triggers the issue for me (resulting in an infinite loop in this case), but since the recompilation is asynchronous, it might require a larger number. Decompiled {{ConditionalEvaluator}} for the test case below: {code:java} import droolstest.Bar; import droolstest.Foo; import java.util.List; import org.drools.core.common.InternalFactHandle; import org.drools.core.common.InternalWorkingMemory; import org.drools.core.rule.Declaration; import org.drools.core.rule.constraint.ConditionEvaluator; import org.drools.core.rule.constraint.EvaluatorHelper; import org.drools.core.spi.Tuple; public class ConditionEvaluator4471f59df9b54235ba1be708b5c480da implements ConditionEvaluator { private static final String EXPRESSION = "!( foo.barNames contains name )"; private final Declaration[] declarations; public boolean evaluate(InternalFactHandle internalFactHandle, InternalWorkingMemory internalWorkingMemory, Tuple tuple) { Tuple tuple2 = tuple; Foo foo = (Foo)this.declarations[0].getValue(internalWorkingMemory, tuple2.getFactHandle().getObject()); List list = foo.getBarNames(); String string = ((Bar)internalFactHandle.getObject()).getName(); return !(list == null ? false : (string == null ? false : EvaluatorHelper.contains((Object)list, (Object)string))); } public ConditionEvaluator4471f59df9b54235ba1be708b5c480da(Declaration[] arrdeclaration) { this.declarations = arrdeclaration; } } {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3572) Show & edit the Test Scenario (Preview) global settings

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3572?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-3572: ---------------------------------- Description: As a user, I want to be able to see and edit the global settings of a Test Scenario (Preview) asset. General properties: - Filename - Scenario Type - Skip/Not to skip (checkbox) Rule available properties: - KieSession: String - KieBase: String - RuleFlowGroup: String DMN available properties: - DMN model path (editable?): String - DMN namespace (is needed?): String - DMN name (is needed?): String was: As a user, I want to be able to see and edit the global settings of a Test Scenario (Preview) asset. [~danielezonca] can you clarify which global settings should be there? KIE Session? Ruleflow groups? ... > Show & edit the Test Scenario (Preview) global settings > ------------------------------------------------------- > > Key: DROOLS-3572 > URL: https://issues.jboss.org/browse/DROOLS-3572 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Klara Kufova > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation > > As a user, I want to be able to see and edit the global settings of a Test Scenario (Preview) asset. > General properties: > - Filename > - Scenario Type > - Skip/Not to skip (checkbox) > Rule available properties: > - KieSession: String > - KieBase: String > - RuleFlowGroup: String > DMN available properties: > - DMN model path (editable?): String > - DMN namespace (is needed?): String > - DMN name (is needed?): String -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4239) Support Locale.forLanguageTag()

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-4239?page=com.atlassian.jira.plugin.... ] Brian Stansberry closed WFLY-4239. ---------------------------------- > Support Locale.forLanguageTag() > -------------------------------- > > Key: WFLY-4239 > URL: https://issues.jboss.org/browse/WFLY-4239 > Project: WildFly > Issue Type: Feature Request > Affects Versions: 9.0.0.Alpha1 > Environment: JDK 7 > Reporter: Romain Pelisse > Assignee: Romain Pelisse > Priority: Minor > Fix For: 9.0.0.CR1 > > > The rules for Locale are different in JDK 6 vs 7, and this getLocale() method was written to conform to the JDK 6 rules. Hence it assumes 2 chars for language, 2 chars for country. Beginning with JDK 7 things are much more complex, and we don't support that. The language can be up to 8 chars, country can be [a-zA-Z]{2} | [0-9]{3}, there's the "script" element, and most importantly, Locale.forLanguageTag(). > It would be nice to at least support Locale.forLanguageTag(). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4239) Support Locale.forLanguageTag()

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-4239?page=com.atlassian.jira.plugin.... ] Brian Stansberry resolved WFLY-4239. ------------------------------------ Resolution: Done > Support Locale.forLanguageTag() > -------------------------------- > > Key: WFLY-4239 > URL: https://issues.jboss.org/browse/WFLY-4239 > Project: WildFly > Issue Type: Feature Request > Affects Versions: 9.0.0.Alpha1 > Environment: JDK 7 > Reporter: Romain Pelisse > Assignee: Romain Pelisse > Priority: Minor > Fix For: 9.0.0.CR1 > > > The rules for Locale are different in JDK 6 vs 7, and this getLocale() method was written to conform to the JDK 6 rules. Hence it assumes 2 chars for language, 2 chars for country. Beginning with JDK 7 things are much more complex, and we don't support that. The language can be up to 8 chars, country can be [a-zA-Z]{2} | [0-9]{3}, there's the "script" element, and most importantly, Locale.forLanguageTag(). > It would be nice to at least support Locale.forLanguageTag(). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4239) Support Locale.forLanguageTag()

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-4239?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-4239: ----------------------------------- Component/s: (was: Localization) > Support Locale.forLanguageTag() > -------------------------------- > > Key: WFLY-4239 > URL: https://issues.jboss.org/browse/WFLY-4239 > Project: WildFly > Issue Type: Feature Request > Affects Versions: 9.0.0.Alpha1 > Environment: JDK 7 > Reporter: Romain Pelisse > Assignee: Romain Pelisse > Priority: Minor > Fix For: 9.0.0.CR1 > > > The rules for Locale are different in JDK 6 vs 7, and this getLocale() method was written to conform to the JDK 6 rules. Hence it assumes 2 chars for language, 2 chars for country. Beginning with JDK 7 things are much more complex, and we don't support that. The language can be up to 8 chars, country can be [a-zA-Z]{2} | [0-9]{3}, there's the "script" element, and most importantly, Locale.forLanguageTag(). > It would be nice to at least support Locale.forLanguageTag(). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4239) Support Locale.forLanguageTag()

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-4239?page=com.atlassian.jira.plugin.... ] Brian Stansberry reopened WFLY-4239: ------------------------------------ > Support Locale.forLanguageTag() > -------------------------------- > > Key: WFLY-4239 > URL: https://issues.jboss.org/browse/WFLY-4239 > Project: WildFly > Issue Type: Feature Request > Components: Localization > Affects Versions: 9.0.0.Alpha1 > Environment: JDK 7 > Reporter: Romain Pelisse > Assignee: Romain Pelisse > Priority: Minor > Fix For: 9.0.0.CR1 > > > The rules for Locale are different in JDK 6 vs 7, and this getLocale() method was written to conform to the JDK 6 rules. Hence it assumes 2 chars for language, 2 chars for country. Beginning with JDK 7 things are much more complex, and we don't support that. The language can be up to 8 chars, country can be [a-zA-Z]{2} | [0-9]{3}, there's the "script" element, and most importantly, Locale.forLanguageTag(). > It would be nice to at least support Locale.forLanguageTag(). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-149) The console-handler in the logging schema still contains a filter element

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-149?page=com.atlassian.jira.plugin.s... ] Brian Stansberry closed WFLY-149. --------------------------------- > The console-handler in the logging schema still contains a filter element > ------------------------------------------------------------------------- > > Key: WFLY-149 > URL: https://issues.jboss.org/browse/WFLY-149 > Project: WildFly > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Fix For: 8.0.0.CR1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-149) The console-handler in the logging schema still contains a filter element

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-149?page=com.atlassian.jira.plugin.s... ] Brian Stansberry resolved WFLY-149. ----------------------------------- Resolution: Done > The console-handler in the logging schema still contains a filter element > ------------------------------------------------------------------------- > > Key: WFLY-149 > URL: https://issues.jboss.org/browse/WFLY-149 > Project: WildFly > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Fix For: 8.0.0.CR1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-149) The console-handler in the logging schema still contains a filter element

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-149?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-149: ---------------------------------- Component/s: Logging (was: Localization) > The console-handler in the logging schema still contains a filter element > ------------------------------------------------------------------------- > > Key: WFLY-149 > URL: https://issues.jboss.org/browse/WFLY-149 > Project: WildFly > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Fix For: 8.0.0.CR1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

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 March 2019