November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3283) Incorrect V&V results when operator is filled in the row (as opposed to column definition)

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-3283?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-3283: --------------------------------- Sprint: 2018 Week 45-47 > Incorrect V&V results when operator is filled in the row (as opposed to column definition) > ------------------------------------------------------------------------------------------ > > Key: DROOLS-3283 > URL: https://issues.jboss.org/browse/DROOLS-3283 > Project: Drools > Issue Type: Bug > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: support > > Imagine data model Person with attribute age. > If you create decision table and add two columns: > - both are defined against "age" attribute > - none of them have operator defined > then you add one row, and you fill in the operator and the value directly inside the row. > For example: > >= 20 > <= 30 > The generated DRL looks like this: > {code:java} > package org; > //from row number: 1 > rule "Row 1 AnotherTest" > dialect "mvel" > when > p : Person( age >= 20 , age <= 30 ) > then > p.setAgeGroup( "whatever" ); > end > {code} > The V&V will report this as conflicting row: > !6iOx.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3282) Should not move to next AgendaGroup even if current is empty

by Edoardo Vacchi (Jira)

Edoardo Vacchi created DROOLS-3282: -------------------------------------- Summary: Should not move to next AgendaGroup even if current is empty Key: DROOLS-3282 URL: https://issues.jboss.org/browse/DROOLS-3282 Project: Drools Issue Type: Bug Reporter: Edoardo Vacchi Assignee: Edoardo Vacchi return nextRule != null && (!ruleAgendaItem.getAgendaGroup().equals( nextRule.getAgendaGroup() ) || !isHigherSalience(nextRule)); -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4204) Add Phase priorities for MicroProfile DUPs

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4204?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4204: -------------------------------- Summary: Add Phase priorities for MicroProfile DUPs (was: Add Phase priorities for MicroProfile DUP) > Add Phase priorities for MicroProfile DUPs > ------------------------------------------ > > Key: WFCORE-4204 > URL: https://issues.jboss.org/browse/WFCORE-4204 > Project: WildFly Core > Issue Type: Bug > Components: Deployment Scanner > Reporter: Jeff Mesnil > Assignee: ehsavoie Hugonnet > Priority: Major > > New MicroProfile extensions were added late in the WildFly 14 release cycles and they did not properly define their priorities in org.jboss.as.server.deployment.Phase. > It introduce 5 new priorities: > {code} > public static final int DEPENDENCIES_MICROPROFILE_CONFIG = 0x1850; > public static final int DEPENDENCIES_MICROPROFILE_METRICS = 0x1860; > public static final int DEPENDENCIES_MICROPROFILE_HEALTH = 0x1870; > public static final int DEPENDENCIES_MICROPROFILE_OPENTRACING = 0x1880; > public static final int POST_MODULE_MICROPROFILE_CONFIG = 0x3750; > public static final int POST_MODULE_MICROPROFILE_METRICS = 0x3760; > public static final int POST_MODULE_MICROPROFILE_HEALTH = 0x3770; > public static final int POST_MODULE_MICROPROFILE_OPENTRACING = 0x3780; > {code} > Note that the metrics priorities correspond to a new extension (tracked by WFLY-10712) that's not in WildFly yet (but will be before 15.0 is released) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4204) Add Phase priorities for MicroProfile DUP

by Jeff Mesnil (Jira)

Jeff Mesnil created WFCORE-4204: ----------------------------------- Summary: Add Phase priorities for MicroProfile DUP Key: WFCORE-4204 URL: https://issues.jboss.org/browse/WFCORE-4204 Project: WildFly Core Issue Type: Bug Components: Deployment Scanner Reporter: Jeff Mesnil Assignee: ehsavoie Hugonnet New MicroProfile extensions were added late in the WildFly 14 release cycles and they did not properly define their priorities in org.jboss.as.server.deployment.Phase. It introduce 5 new priorities: {code} public static final int DEPENDENCIES_MICROPROFILE_CONFIG = 0x1850; public static final int DEPENDENCIES_MICROPROFILE_METRICS = 0x1860; public static final int DEPENDENCIES_MICROPROFILE_HEALTH = 0x1870; public static final int DEPENDENCIES_MICROPROFILE_OPENTRACING = 0x1880; public static final int POST_MODULE_MICROPROFILE_CONFIG = 0x3750; public static final int POST_MODULE_MICROPROFILE_METRICS = 0x3760; public static final int POST_MODULE_MICROPROFILE_HEALTH = 0x3770; public static final int POST_MODULE_MICROPROFILE_OPENTRACING = 0x3780; {code} Note that the metrics priorities correspond to a new extension (tracked by WFLY-10712) that's not in WildFly yet (but will be before 15.0 is released) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3162) Resolve Table (grid) width for Scenario

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3162?page=com.atlassian.jira.plugi... ] Daniele Zonca reassigned DROOLS-3162: ------------------------------------- Assignee: Daniele Zonca (was: Gabriele Cardosi) > Resolve Table (grid) width for Scenario > --------------------------------------- > > Key: DROOLS-3162 > URL: https://issues.jboss.org/browse/DROOLS-3162 > Project: Drools > Issue Type: Sub-task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Daniele Zonca > Priority: Major > Labels: UX-CSS > > Table does not extend to the full width of the canvas area, which in the default view creates a gap between the table and the right panel. This could affect usability as the visual association and proximity between the selected cell and the input area (in the right panel) is reduced. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-1663) BC FIPS, Management Interface, ELY04001: No algorithm found matching TLS/SSL protocol selection criteria

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/ELY-1663?page=com.atlassian.jira.plugin.s... ] Martin Choma commented on ELY-1663: ----------------------------------- I can confirm with the fix I dont see tests failing anymore. > BC FIPS, Management Interface, ELY04001: No algorithm found matching TLS/SSL protocol selection criteria > -------------------------------------------------------------------------------------------------------- > > Key: ELY-1663 > URL: https://issues.jboss.org/browse/ELY-1663 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Affects Versions: 1.6.0.Final > Reporter: Martin Choma > Assignee: Farah Juma > Priority: Blocker > > Rarely 1:30 it happens there occures error accessing http management interface secured with TLS with BC FIPS > {code} > Operation {"operation" => "add","address" => [("subsystem" => "elytron"),("server-ssl-context" => "test-server-ssl-context")],"key-manager" => "key-manager-name_test-server-ssl-context","cipher-suite-filter" => "TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA,TLS_DHE_DSS_WITH_AES_128_CBC_SHA,TLS_DHE_DSS_WITH_AES_128_CBC_SHA256,TLS_DHE_DSS_WITH_AES_256_CBC_SHA,TLS_DHE_DSS_WITH_AES_256_CBC_SHA256,TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_3DES_EDE_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA256","trust-manager" => "trust-manager-name_test-server-ssl-context","protocols" => ["TLSv1.2"],"need-client-auth" => true} failed: {"outcome" => "failed","failure-description" => {"WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.test-server-ssl-context" => "java.security.NoSuchAlgorithmException: ELY04001: No algorithm found matching TLS/SSL protocol selection criteria > Caused by: java.security.NoSuchAlgorithmException: ELY04001: No algorithm found matching TLS/SSL protocol selection criteria"}},"rolled-back" => true} > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service org.wildfly.security.ssl-context.test-server-ssl-context: org.jboss.msc.service.StartException in service org.wildfly.security.ssl-context.test-server-ssl-context: java.security.NoSuchAlgorithmException: ELY04001: No algorithm found matching TLS/SSL protocol selection criteria > at org.wildfly.extension.elytron.SSLDefinitions$6.lambda$getValueSupplier$1(SSLDefinitions.java:982) > at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.security.NoSuchAlgorithmException: ELY04001: No algorithm found matching TLS/SSL protocol selection criteria > at org.wildfly.security.ssl.SSLUtils.lambda$createSslContextFactory$1(SSLUtils.java:130) > at org.wildfly.security.ssl.SSLContextBuilder.lambda$build$0(SSLContextBuilder.java:340) > at org.wildfly.security.OneTimeSecurityFactory.create(OneTimeSecurityFactory.java:53) > at org.wildfly.extension.elytron.SSLDefinitions$6.lambda$getValueSupplier$1(SSLDefinitions.java:980) > ... 9 more > {code} > Some facts > * It happens only on management interface BC FIPS TLS tests > * It does not occur on Undertow secured with BC FIPS > * Previously there was issue with similar error but that happened everywhere https://issues.jboss.org/browse/ELY-1618 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3281) [DMN Designer] The output name is valorized for single output decision table

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-3281: -------------------------------------- Summary: [DMN Designer] The output name is valorized for single output decision table Key: DROOLS-3281 URL: https://issues.jboss.org/browse/DROOLS-3281 Project: Drools Issue Type: Bug Components: DMN Editor Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3281) [DMN Designer] The output name is valorized for single output decision table

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-3281?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-3281: ----------------------------------- Labels: drools-tools (was: ) > [DMN Designer] The output name is valorized for single output decision table > ---------------------------------------------------------------------------- > > Key: DROOLS-3281 > URL: https://issues.jboss.org/browse/DROOLS-3281 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > Labels: drools-tools > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3280) DMNRuntime API for evaluateByID/Name to error if empty array

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-3280: -------------------------------------- Summary: DMNRuntime API for evaluateByID/Name to error if empty array Key: DROOLS-3280 URL: https://issues.jboss.org/browse/DROOLS-3280 Project: Drools Issue Type: Enhancement Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4148) Check and consider to put escaped quotes (\") back to the -Xloggc in standalone.sh

by Radovan Stancel (Jira)

[ https://issues.jboss.org/browse/WFCORE-4148?page=com.atlassian.jira.plugi... ] Radovan Stancel commented on WFCORE-4148: ----------------------------------------- [~jamezp] PR was rebased > Check and consider to put escaped quotes (\") back to the -Xloggc in standalone.sh > ---------------------------------------------------------------------------------- > > Key: WFCORE-4148 > URL: https://issues.jboss.org/browse/WFCORE-4148 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Reporter: Marek Kopecký > Assignee: Radovan Stancel > Priority: Major > > Check and consider to put escaped quotes (\") back to the -Xloggc in standalone.sh > See the discussion [here|https://github.com/wildfly/wildfly-core/pull/3496#discussion_r221509989] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 6 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 November 2018