August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-916) E2E - External Service TC Bug

by Matthew Mahoney (Jira)

Matthew Mahoney created SWSQE-916: ------------------------------------- Summary: E2E - External Service TC Bug Key: SWSQE-916 URL: https://issues.jboss.org/browse/SWSQE-916 Project: Kiali QE Issue Type: Bug Reporter: Matthew Mahoney Assignee: Matthew Mahoney -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4591) Bump logging schema and model versions

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4591?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4591: ---------------------------------- Description: The logging subsystem schema needs to be bumped from 7.0 to 8.0. The logging subsystem model version needs to be bumped from 8.0.0 to 9.0.0. (was: The logging subsystem schema needs to be bumped from 6.0 to 7.0. The logging subsystem model version needs to be bumped from 7.0.0 to 8.0.0.) > Bump logging schema and model versions > -------------------------------------- > > Key: WFCORE-4591 > URL: https://issues.jboss.org/browse/WFCORE-4591 > Project: WildFly Core > Issue Type: Task > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > The logging subsystem schema needs to be bumped from 7.0 to 8.0. The logging subsystem model version needs to be bumped from 8.0.0 to 9.0.0. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4591) Bump logging schema and model versions

by James Perkins (Jira)

James Perkins created WFCORE-4591: ------------------------------------- Summary: Bump logging schema and model versions Key: WFCORE-4591 URL: https://issues.jboss.org/browse/WFCORE-4591 Project: WildFly Core Issue Type: Task Components: Logging Reporter: James Perkins Assignee: James Perkins Fix For: 9.0.0.Beta3, 9.0.0.Final The logging subsystem schema needs to be bumped from 6.0 to 7.0. The logging subsystem model version needs to be bumped from 7.0.0 to 8.0.0. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4591) Bump logging schema and model versions

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4591?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4591: ---------------------------------- Fix Version/s: (was: 9.0.0.Beta3) (was: 9.0.0.Final) > Bump logging schema and model versions > -------------------------------------- > > Key: WFCORE-4591 > URL: https://issues.jboss.org/browse/WFCORE-4591 > Project: WildFly Core > Issue Type: Task > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > The logging subsystem schema needs to be bumped from 6.0 to 7.0. The logging subsystem model version needs to be bumped from 7.0.0 to 8.0.0. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4591) Bump logging schema and model versions

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4591?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4591: ---------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly-core/pull/3678) > Bump logging schema and model versions > -------------------------------------- > > Key: WFCORE-4591 > URL: https://issues.jboss.org/browse/WFCORE-4591 > Project: WildFly Core > Issue Type: Task > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > The logging subsystem schema needs to be bumped from 6.0 to 7.0. The logging subsystem model version needs to be bumped from 7.0.0 to 8.0.0. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4372) DMN Editor Data type usability study: design assets

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4372?page=com.atlassian.jira.plugi... ] Elizabeth Clayton resolved DROOLS-4372. --------------------------------------- Resolution: Done > DMN Editor Data type usability study: design assets > --------------------------------------------------- > > Key: DROOLS-4372 > URL: https://issues.jboss.org/browse/DROOLS-4372 > Project: Drools > Issue Type: Task > Components: DMN Editor > Environment: Version 7.4 > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, Usability, drools-tools > > Description: > * Create a study plan outline. > * Review usability study materials. > * Create a click-thru wireframe prototype for a lightweight usability study to test the ease of use in viewing, creating, editing and deleting data types, particularly structured data types. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

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

by Ashley Abdel-Sayed (Jira)

[ https://issues.jboss.org/browse/ELY-1819?page=com.atlassian.jira.plugin.s... ] Ashley Abdel-Sayed reassigned ELY-1819: --------------------------------------- Assignee: Ashley Abdel-Sayed > 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 > Assignee: Ashley Abdel-Sayed > 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)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4395) The single mapper validation added via WFCORE-2364 happens at Runtime, this should be a Model time check.

by Ashley Abdel-Sayed (Jira)

[ https://issues.jboss.org/browse/WFCORE-4395?page=com.atlassian.jira.plugi... ] Ashley Abdel-Sayed commented on WFCORE-4395: -------------------------------------------- [~dlofthouse] Could you let me know how I can reproduce that error for unsatisfied dependencies? > The single mapper validation added via WFCORE-2364 happens at Runtime, this should be a Model time check. > --------------------------------------------------------------------------------------------------------- > > Key: WFCORE-4395 > URL: https://issues.jboss.org/browse/WFCORE-4395 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Darran Lofthouse > Assignee: Ashley Abdel-Sayed > Priority: Major > > If possible the mappers should be flagged as being mutually exclusive, however failing that the validation should happen during Stage.MODEL. > Presently this leads to an unsatisifed dependency: - > {noformat} > 14:21:59,055 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "elytron"), > ("security-domain" => "demon-domain") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.security-realm.demo-realm"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.security.security-domain.demon-domain.initial is missing [org.wildfly.security.security-realm.demo-realm]"] > } > {noformat} > Despite this error the underlying cause is not logged at any level. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4372) DMN Editor Data type usability study: design assets

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4372?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-4372: ------------------------------------------- [~sarahjane] [~karreiro] I'm marking this jira as Resolved, but if you need anything else for the study just let me know. Thanks! > DMN Editor Data type usability study: design assets > --------------------------------------------------- > > Key: DROOLS-4372 > URL: https://issues.jboss.org/browse/DROOLS-4372 > Project: Drools > Issue Type: Task > Components: DMN Editor > Environment: Version 7.4 > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, Usability, drools-tools > > Description: > * Create a study plan outline. > * Review usability study materials. > * Create a click-thru wireframe prototype for a lightweight usability study to test the ease of use in viewing, creating, editing and deleting data types, particularly structured data types. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4258) DMN UX - overlay information about a single scenario run

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4258?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-4258: ------------------------------------------- [~mmenestr][~danielezonca] If the solution falls more on the DMN side than that Scenario side please feel free to reassign it to me. > DMN UX - overlay information about a single scenario run > -------------------------------------------------------- > > Key: DROOLS-4258 > URL: https://issues.jboss.org/browse/DROOLS-4258 > Project: Drools > Issue Type: Story > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Daniele Zonca > Assignee: Margot Menestrot > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam, drools-tools > > Related to https://issues.jboss.org/browse/DROOLS-3731 > This task will cover this use case: > - user creates a DMN model > - user creates a Test Scenario with some scenarios > - user executes the Test Scenario > - user open Coverage Report > - user wants to analyze the execution of a *single scenario* in the DMN model > - user clicks on "a link" related to the scenario to analyze > - user lands on DMN editor with overlay information about decision executed, decision failed and for each decision the possibility see actual and expected value (from the scenario) and to open an executed decision table to see which row has been evaluated -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 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 August 2019