January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4943) Guided Decision Table Validation and Verification feature is broken

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4943?page=com.atlassian.jira.plug... ] Toni Rikkola commented on DROOLS-4943: -------------------------------------- Sounds like the good old "full build not executed" issue. Now that the V&V is in the panel I think we need to make the GWT build run by default. And just to make it easier to test. > Guided Decision Table Validation and Verification feature is broken > ------------------------------------------------------------------- > > Key: DROOLS-4943 > URL: https://issues.redhat.com/browse/DROOLS-4943 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Blocker > Labels: drools-tools > Attachments: Screenshot from 2020-01-16 16-01-08.png > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4943) Guided Decision Table Validation and Verification feature is broken

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-4943?page=com.atlassian.jira.plug... ] Toni Rikkola edited comment on DROOLS-4943 at 1/16/20 11:41 AM: ---------------------------------------------------------------- I tried with -Dfull and it worked. Sounds like the good old "full build not executed" issue. Now that the V&V is in the panel I think we need to make the GWT build run by default. And just to make it easier to test. was (Author: rikkola): Sounds like the good old "full build not executed" issue. Now that the V&V is in the panel I think we need to make the GWT build run by default. And just to make it easier to test. > Guided Decision Table Validation and Verification feature is broken > ------------------------------------------------------------------- > > Key: DROOLS-4943 > URL: https://issues.redhat.com/browse/DROOLS-4943 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Blocker > Labels: drools-tools > Attachments: Screenshot from 2020-01-16 16-01-08.png > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12983) Upgrade JBoss SAAJ to 1.0.2.Final

by Darran Lofthouse (Jira)

Darran Lofthouse created WFLY-12983: --------------------------------------- Summary: Upgrade JBoss SAAJ to 1.0.2.Final Key: WFLY-12983 URL: https://issues.redhat.com/browse/WFLY-12983 Project: WildFly Issue Type: Component Upgrade Components: Web Services Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 19.0.0.Beta1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4800) Add an env var driven expression to the standard deployment scanner scan-interval

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4800: ---------------------------------------- Summary: Add an env var driven expression to the standard deployment scanner scan-interval Key: WFCORE-4800 URL: https://issues.redhat.com/browse/WFCORE-4800 Project: WildFly Core Issue Type: Enhancement Components: Deployment Scanner Reporter: Brian Stansberry Assignee: Emmanuel Hugonnet Recurring deployment scans in a production container don't make a lot of sense. But our standard container images do rely on the boot time scan, so we don't want to just not use the scanner in images. A middle ground is to make it easy to turn off the recurring scans by using an expression for our standard config's scanner interval, instead of the static "5000". Default would still be 5000 for compatibility. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4943) Guided Decision Table Validation and Verification feature is broken

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-4943?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-4943: -------------------------------------- Assignee: Toni Rikkola (was: Michael Anstis) > Guided Decision Table Validation and Verification feature is broken > ------------------------------------------------------------------- > > Key: DROOLS-4943 > URL: https://issues.redhat.com/browse/DROOLS-4943 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Blocker > Labels: drools-tools > Attachments: Screenshot from 2020-01-16 16-01-08.png > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4943) Guided Decision Table Validation and Verification feature is broken

by Jozef Marko (Jira)

Jozef Marko created DROOLS-4943: ----------------------------------- Summary: Guided Decision Table Validation and Verification feature is broken Key: DROOLS-4943 URL: https://issues.redhat.com/browse/DROOLS-4943 Project: Drools Issue Type: Bug Components: Guided Decision Table Editor Affects Versions: 7.32.0.Final Reporter: Jozef Marko Assignee: Michael Anstis Attachments: Screenshot from 2020-01-16 16-01-08.png -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10852) smallrye-config: Consider logging a message when properties with same key and ordinal are present

by Michal Jurc (Jira)

[ https://issues.redhat.com/browse/WFLY-10852?page=com.atlassian.jira.plugi... ] Michal Jurc updated WFLY-10852: ------------------------------- Tester: Jan Stourac > smallrye-config: Consider logging a message when properties with same key and ordinal are present > ------------------------------------------------------------------------------------------------- > > Key: WFLY-10852 > URL: https://issues.redhat.com/browse/WFLY-10852 > Project: WildFly > Issue Type: Enhancement > Components: MP Config > Reporter: Michal Jurc > Assignee: Jeff Mesnil > Priority: Major > > Consider a deployment with default {{microprofile-config.properties}}: > {code}managementDefault=Default value from default microprofile-config.properties{code} > Deployment is deployed on server with the following {{ConfigSource}} defined: > {code}[standalone@localhost:9990 /] /subsystem=microprofile-config-smallrye/config-source=testdefault:read-resource > { > "outcome" => "success", > "result" => { > "class" => undefined, > "dir" => undefined, > "ordinal" => 100, > "properties" => {"managementDefault" => "Value from WildFly microprofile-config-smallrye config-source"} > } > } > {code} > Property {{"managementDefault"}} is always resolved to {{"Value from WildFly microprofile-config-smallrye config-source"}} in deployment. > It would be useful to log a {{WARN}} level message when there is conflict like this with a notification of {{ConfigSources}} to save detective work in real world scenarios. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10850) smallrye-config: Allow configuration of per-deployment DirConfigSource

by Michal Jurc (Jira)

[ https://issues.redhat.com/browse/WFLY-10850?page=com.atlassian.jira.plugi... ] Michal Jurc updated WFLY-10850: ------------------------------- Tester: Jan Stourac > smallrye-config: Allow configuration of per-deployment DirConfigSource > ---------------------------------------------------------------------- > > Key: WFLY-10850 > URL: https://issues.redhat.com/browse/WFLY-10850 > Project: WildFly > Issue Type: Enhancement > Components: MP Config > Reporter: Michal Jurc > Assignee: Jeff Mesnil > Priority: Major > > With the current integration of {{smallrye-config}} with WildFly, it is possible to add a {{config-source}} management element that will hold a location of property directory. In cloud environments, it would be handier to allow this configuration to be committed from deployment itself. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10849) Allow for configuration of Converter SPI implementations via management in microprofile-config-smallrye subsystem

by Michal Jurc (Jira)

[ https://issues.redhat.com/browse/WFLY-10849?page=com.atlassian.jira.plugi... ] Michal Jurc updated WFLY-10849: ------------------------------- Tester: Jan Stourac > Allow for configuration of Converter SPI implementations via management in microprofile-config-smallrye subsystem > ----------------------------------------------------------------------------------------------------------------- > > Key: WFLY-10849 > URL: https://issues.redhat.com/browse/WFLY-10849 > Project: WildFly > Issue Type: Enhancement > Components: MP Config > Reporter: Michal Jurc > Assignee: Jeff Mesnil > Priority: Major > > MicroProfile configuration specifies three SPIs: > * {{org.eclipse.microprofile.config.spi.ConfigSource}} > * {{org.eclipse.microprofile.config.spi.ConfigSourceProvider}} > * {{org.eclipse.microprofile.config.spi.Converter}} > {{ConfigSource}} and {{ConfigSourceProvider}} services both can be exposed by WildFly management. We recommend providing the same capability for {{Converter}} services. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8793) Change attributes of services in EJB3 subsystem to allow runtime modifications

by Michal Jurc (Jira)

[ https://issues.redhat.com/browse/WFLY-8793?page=com.atlassian.jira.plugin... ] Michal Jurc updated WFLY-8793: ------------------------------ Tester: Jan Blizňák > Change attributes of services in EJB3 subsystem to allow runtime modifications > ------------------------------------------------------------------------------ > > Key: WFLY-8793 > URL: https://issues.redhat.com/browse/WFLY-8793 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Michal Jurc > Priority: Major > > Currently, almost all of the attributes of services in {{/subsystem=ejb3}} have {{"restart-required" => "all-services"}}. This should be changed to allow these attributes to be modifiable in runtime where possible. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 2020