June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12170) Upgrade wildfly-transaction-client from 1.1.3.Final to 1.1.4.Final

by Ingo Weiss (Jira)

Ingo Weiss created WFLY-12170: --------------------------------- Summary: Upgrade wildfly-transaction-client from 1.1.3.Final to 1.1.4.Final Key: WFLY-12170 URL: https://issues.jboss.org/browse/WFLY-12170 Project: WildFly Issue Type: Component Upgrade Components: EJB Affects Versions: 17.0.0.Beta1 Reporter: Ingo Weiss Assignee: Cheng Fang https://github.com/wildfly/wildfly-transaction-client/compare/1.1.3.Final... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1818) Don't use a lambda for the disposal of mechanisms in forEach

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1818?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1818: ---------------------------------- Fix Version/s: 1.10.0.CR1 (was: 1.9.2.CR1) > Don't use a lambda for the disposal of mechanisms in forEach > ------------------------------------------------------------ > > Key: ELY-1818 > URL: https://issues.jboss.org/browse/ELY-1818 > Project: WildFly Elytron > Issue Type: Bug > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.10.0.CR1 > > > A simple for loop will be sufficient without needing a lambda defining and instantiating. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1816) Ensure a source jar is created for the common test module

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1816?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1816: ---------------------------------- Fix Version/s: 1.10.0.CR1 > Ensure a source jar is created for the common test module > --------------------------------------------------------- > > Key: ELY-1816 > URL: https://issues.jboss.org/browse/ELY-1816 > Project: WildFly Elytron > Issue Type: Task > Components: Testsuite > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.9.2.CR1, 1.10.0.CR1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1819) The logout handler registration should be reworked

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1819?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse reassigned ELY-1819: ------------------------------------- Assignee: (was: Darran Lofthouse) > The logout handler registration should be reworked > -------------------------------------------------- > > Key: ELY-1819 > URL: https://issues.jboss.org/browse/ELY-1819 > Project: WildFly Elytron > Issue Type: Bug > Components: HTTP > Reporter: Darran Lofthouse > Priority: Major > Fix For: 1.9.2.CR1 > > > Presently the logout handler is just a Runnable, the problem with this is if it needs any state it means a lambda or an instance of a class tends to be needed to hold the state e.g. > {noformat} > private void setupProgramaticLogout(HttpScope sessionScope) { > logoutHandlerConsumer.accept(() -> { > sessionScope.setAttachment(AUTHENTICATED_IDENTITY_KEY, null); > }); > } > {noformat} > It would likely be better for the logout handler to be able to request the scope it needs so maybe pass in the 'org.wildfly.security.http.HttpServerScopes' at the very least. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1820) SecurityProviderServerMechanismFactory should support Provider instances

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1820?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1820: ---------------------------------- Fix Version/s: 1.10.0.CR1 (was: 1.9.2.CR1) > SecurityProviderServerMechanismFactory should support Provider instances > ------------------------------------------------------------------------ > > Key: ELY-1820 > URL: https://issues.jboss.org/browse/ELY-1820 > Project: WildFly Elytron > Issue Type: Bug > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.10.0.CR1 > > > In many cases we already have the Provider instance or instances, we should not require an intermediate Supplier instance which encourages the use of a lambda just to pass these in. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4136) R&D how to run scenario simulation tests inside VSCode

by Eder Ignatowicz (Jira)

Eder Ignatowicz created DROOLS-4136: --------------------------------------- Summary: R&D how to run scenario simulation tests inside VSCode Key: DROOLS-4136 URL: https://issues.jboss.org/browse/DROOLS-4136 Project: Drools Issue Type: Task Reporter: Eder Ignatowicz Assignee: Gabriele Cardosi The main goal of this JIRA is to research what are the best approaches in order to run scenario simulation tests inside VSCode client-side only distribution. Eder's first ideas: [1] Run kie-server inside a docker image and run scenario tests via REST API [2] Show the result of test execution inside scenario simulation editor <add your idea here> On future: [1] + investigate if it's possible to show tests execution results inside another junit vscode extension -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1821) ProviderUtil should contain overloaded methods which accept arrays of Providers

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1821?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1821: ---------------------------------- Fix Version/s: 1.10.0.CR1 (was: 1.9.2.CR1) > ProviderUtil should contain overloaded methods which accept arrays of Providers > ------------------------------------------------------------------------------- > > Key: ELY-1821 > URL: https://issues.jboss.org/browse/ELY-1821 > Project: WildFly Elytron > Issue Type: Bug > Components: Utils > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.10.0.CR1 > > > Presently the methods only accept Supplier<Provider[]> - this means even if you have an array of Provider instances it needs wrapping in a Supplier just to use these methods. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4134) Create a scenario simulation distribution

by Eder Ignatowicz (Jira)

Eder Ignatowicz created DROOLS-4134: --------------------------------------- Summary: Create a scenario simulation distribution Key: DROOLS-4134 URL: https://issues.jboss.org/browse/DROOLS-4134 Project: Drools Issue Type: Task Reporter: Eder Ignatowicz Assignee: Gabriele Cardosi Create a scenario simulation client-side editor based on our base showcase. This editor will only be able to do a simple POC inside VSCode. For now, we will have a mocked marshaller and we will not run/execute any test scenario. Moreover, also the base data used to create the scenario simulation (DMOs/DMNs) will be hardcoded The end result of this JIRA is a scenario simulation editor visible inside VSCode with mocked data. This war should be manually included inside the current VSCode extension. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1823) Update SecurityProviderServerMechanismFactory to cache Provider interaction.

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1823?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1823: ---------------------------------- Fix Version/s: 1.10.0.CR1 (was: 1.9.2.CR1) > Update SecurityProviderServerMechanismFactory to cache Provider interaction. > ---------------------------------------------------------------------------- > > Key: ELY-1823 > URL: https://issues.jboss.org/browse/ELY-1823 > Project: WildFly Elytron > Issue Type: Enhancement > Components: HTTP > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.10.0.CR1 > > > The SecurityProviderServerMechanismFactory regularly interacts with the Provider which can cause contention as calls to getServices() and getService(S,S) are synchronized. > Runtime updates are not actually expected so we should cache the interactions. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4135) Scenario Simulation Marshaller

by Eder Ignatowicz (Jira)

Eder Ignatowicz created DROOLS-4135: --------------------------------------- Summary: Scenario Simulation Marshaller Key: DROOLS-4135 URL: https://issues.jboss.org/browse/DROOLS-4135 Project: Drools Issue Type: Task Reporter: Eder Ignatowicz Assignee: Gabriele Cardosi <TODO after Marshaller BAPL> -- 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 June 2019