April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2465) Remove use_ip_addrs

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2465?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2465: --------------------------- Description: Remove {{use_ip_addrs}}; nobody uses this and it complicates the code. Also remove {{NAMING}}. (was: Remove {{use_ip_addrs}}; nobody uses this and it complicates the code) > Remove use_ip_addrs > ------------------- > > Key: JGRP-2465 > URL: https://issues.redhat.com/browse/JGRP-2465 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0.0.Alpha4 > > > Remove {{use_ip_addrs}}; nobody uses this and it complicates the code. Also remove {{NAMING}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13347) Remove org.apache.xml-resolver (it has been moved to WildFly)

by Kabir Khan (Jira)

Kabir Khan created WFLY-13347: --------------------------------- Summary: Remove org.apache.xml-resolver (it has been moved to WildFly) Key: WFLY-13347 URL: https://issues.redhat.com/browse/WFLY-13347 Project: WildFly Issue Type: Task Components: Web Services Reporter: Brian Stansberry Assignee: Parul Sharma The org.apache.xml-resolver module is not used by WildFly Core. Only use is in full: {code} $ git grep xml-resolver | grep module.x feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/impl/main/module.xml: <module name="org.apache.xml-resolver" /> feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/main/module.xml: <module name="org.apache.xml-resolver" /> feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/services-sts/main/module.xml: <module name="org.apache.xml-resolver" /> feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/ws-security/main/module.xml: <module name="org.apache.xml-resolver" /> {code} Moving it will tidy things up some and perhaps avoid any special handling for it as Galleon layers work continues. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4911) Remove org.apache.xml-resolver (it has been moved to WildFly)

by Kabir Khan (Jira)

[ https://issues.redhat.com/browse/WFCORE-4911?page=com.atlassian.jira.plug... ] Kabir Khan moved WFLY-13347 to WFCORE-4911: ------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-4911 (was: WFLY-13347) Component/s: XML Frameworks (was: Web Services) > Remove org.apache.xml-resolver (it has been moved to WildFly) > ------------------------------------------------------------- > > Key: WFCORE-4911 > URL: https://issues.redhat.com/browse/WFCORE-4911 > Project: WildFly Core > Issue Type: Task > Components: XML Frameworks > Reporter: Brian Stansberry > Assignee: Parul Sharma > Priority: Minor > > The org.apache.xml-resolver module is not used by WildFly Core. Only use is in full: > {code} > $ git grep xml-resolver | grep module.x > feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/impl/main/module.xml: <module name="org.apache.xml-resolver" /> > feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/main/module.xml: <module name="org.apache.xml-resolver" /> > feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/services-sts/main/module.xml: <module name="org.apache.xml-resolver" /> > feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/ws-security/main/module.xml: <module name="org.apache.xml-resolver" /> > {code} > Moving it will tidy things up some and perhaps avoid any special handling for it as Galleon layers work continues. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5132) DMN Drools TCK runner updates

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5132?page=com.atlassian.jira.plug... ] Matteo Mortari commented on DROOLS-5132: ---------------------------------------- When resolving this jira, evaluate to move upstream DMN TCK Drools runner to use "typecheck" flag, instead of "strictconformance" flag > DMN Drools TCK runner updates > ----------------------------- > > Key: DROOLS-5132 > URL: https://issues.redhat.com/browse/DROOLS-5132 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > Activities on upstream DMN TCK is on hold as no meetings are being held -> no PRs merged on DMN TCK repo. > Hence this PR is pending: https://github.com/dmn-tck/tck/pull/360 > In that branch/PR, I am aligning with the original TCK intention that "errorResult" flag is an hint, but cannot be enforced, over the runners. > Example, in case > * the result from a DMN expression evaluation is null, > * the TCK expect a null, > * IFF TCK did not flagged as "errorResult", we no longer just fail simply because the Drools DMN engine reported an error (which was not indicated by the TCK test). > https://github.com/dmn-tck/tck/pull/360/files#diff-49ce6a21913fba22bc06e7... > Before, if the Drools DMN engine raised an error, but the TCK did not indicated as "errorResult" we were reporting a failure, even if the actual value was consistent with the expected one! > Now is aligned as explained. > Naturally, I've in parallel raised already PR to TCK to fix the test and to provide the proper "errorResult" hint. (https://github.com/dmn-tck/tck/pull/359) > Once the DMN-TCK-upstream PR for the Drools TCK runner is merged, the commit https://github.com/kiegroup/drools/commit/ca70199cf5edccf5261f153dde3296c... can be reverted. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5203) Make DMN Validator use generic V&V module for conflicting, misleading, masked and overlapping rows

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-5203?page=com.atlassian.jira.plug... ] Toni Rikkola commented on DROOLS-5203: -------------------------------------- [~jomarko] I'll use this ticket as the main ticket describing and delivering the PRs. > Make DMN Validator use generic V&V module for conflicting, misleading, masked and overlapping rows > -------------------------------------------------------------------------------------------------- > > Key: DROOLS-5203 > URL: https://issues.redhat.com/browse/DROOLS-5203 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Goal is to merge and reuse the existing generic validator for the issue types in the title. The user should see no difference in the workbench use, but this will help us to reduce reduncancy and improve future V&V coverage for both DMN and DRL at the same time. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5203) Make DMN Validator use generic V&V module for conflicting, misleading, masked and overlapping rows

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-5203?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-5203: --------------------------------- Tester: Jozef Marko > Make DMN Validator use generic V&V module for conflicting, misleading, masked and overlapping rows > -------------------------------------------------------------------------------------------------- > > Key: DROOLS-5203 > URL: https://issues.redhat.com/browse/DROOLS-5203 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Goal is to merge and reuse the existing generic validator for the issue types in the title. The user should see no difference in the workbench use, but this will help us to reduce reduncancy and improve future V&V coverage for both DMN and DRL at the same time. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5203) Make DMN Validator use generic V&V module for conflicting, misleading, masked and overlapping rows

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-5203?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-5203: --------------------------------- Description: Goal is to merge and reuse the existing generic validator for the issue types in the title. The user should see no difference in the workbench use, but this will help us to reduce reduncancy and improve future V&V coverage for both DMN and DRL at the same time. > Make DMN Validator use generic V&V module for conflicting, misleading, masked and overlapping rows > -------------------------------------------------------------------------------------------------- > > Key: DROOLS-5203 > URL: https://issues.redhat.com/browse/DROOLS-5203 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Goal is to merge and reuse the existing generic validator for the issue types in the title. The user should see no difference in the workbench use, but this will help us to reduce reduncancy and improve future V&V coverage for both DMN and DRL at the same time. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2374) TCP/TCP_NIO2: add TLS

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2374?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2374: --------------------------- Fix Version/s: 5.1 (was: 5.0.0.Alpha4) > TCP/TCP_NIO2: add TLS > --------------------- > > Key: JGRP-2374 > URL: https://issues.redhat.com/browse/JGRP-2374 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.1 > > > Add TLS to the TCP and TCP_NIO2 transports. Look into wildfly-openssl [1] for the impl. > [1] https://github.com/wildfly-security/wildfly-openssl -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2430) GossipRouter: more efficient routing

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2430?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2430: --------------------------- Fix Version/s: 5.1 (was: 5.0.0.Alpha4) > GossipRouter: more efficient routing > ------------------------------------ > > Key: JGRP-2430 > URL: https://issues.redhat.com/browse/JGRP-2430 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.1 > > > GossipRouter supports both NIO (ByteBuffer) and TCP (stream-based) connections. In both cases, however, the entire message is read and then routed to the destination address. > It would be better to only read the cluster name and target address, and then use efficient stream-to-stream (or channel-to-channel) _transfer mechanisms_, which avoids temporary copies of data and the full reading of messages. > Also look into routing of entire message _batches_. > Investigate whether this is possible. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5132) DMN Drools TCK runner updates

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5132?page=com.atlassian.jira.plug... ] Matteo Mortari commented on DROOLS-5132: ---------------------------------------- CRITERIA FOR RESOLVING THIS JIRA as of 2020-04-08: revert for kie-dmn-tck to use TCK upstream repo's master branch, might require reverting multiple commits of kie-dmn-tck pom.xml > DMN Drools TCK runner updates > ----------------------------- > > Key: DROOLS-5132 > URL: https://issues.redhat.com/browse/DROOLS-5132 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > Activities on upstream DMN TCK is on hold as no meetings are being held -> no PRs merged on DMN TCK repo. > Hence this PR is pending: https://github.com/dmn-tck/tck/pull/360 > In that branch/PR, I am aligning with the original TCK intention that "errorResult" flag is an hint, but cannot be enforced, over the runners. > Example, in case > * the result from a DMN expression evaluation is null, > * the TCK expect a null, > * IFF TCK did not flagged as "errorResult", we no longer just fail simply because the Drools DMN engine reported an error (which was not indicated by the TCK test). > https://github.com/dmn-tck/tck/pull/360/files#diff-49ce6a21913fba22bc06e7... > Before, if the Drools DMN engine raised an error, but the TCK did not indicated as "errorResult" we were reporting a failure, even if the actual value was consistent with the expected one! > Now is aligned as explained. > Naturally, I've in parallel raised already PR to TCK to fix the test and to provide the proper "errorResult" hint. (https://github.com/dmn-tck/tck/pull/359) > Once the DMN-TCK-upstream PR for the Drools TCK runner is merged, the commit https://github.com/kiegroup/drools/commit/ca70199cf5edccf5261f153dde3296c... can be reverted. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2020