August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4408) [DMN Designer] Search feature - Highlight all search results in the Guided Decision Table editor and Guided Decision Table editor graph

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4408?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-4408: ------------------------------------ Sprint: (was: 2019 Week 32-34) > [DMN Designer] Search feature - Highlight all search results in the Guided Decision Table editor and Guided Decision Table editor graph > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-4408 > URL: https://issues.jboss.org/browse/DROOLS-4408 > Project: Drools > Issue Type: Task > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > Currently, only the current result is highlighted when the user performs a search. However, all search results must be is highlighted. > Apply the infrastructure code from https://issues.jboss.org/browse/DROOLS-4406 to highlight the grid cells and pure CSS into the Data Types tab. > ⚠️ Notice: > Each search must be executed in 500ms tops. If this target is not feasible, the JIRA must be closed without resolution. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12361) Restructure High Availability Guide

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12361?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12361: ---------------------------------- Description: After migration to adoc, the headlines got converted incorrectly, while at this we want to reshuffle this to correspond more with: # Introduction To High Availability Services # Distributable Web Applications # EJB Services # Clustering API # Singleton deployments # Singleton MSC services # Infinispan Subsystem # JGroups Subsystem # Singleton subsystem # mod_cluster Subsystem # Clustering and Domain Setup Walkthrough was: After migration to adoc, the headlines got converted incorrectly, while at this we want to reshuffle this to correspond more with: # Introduction To High Availability Services # Distributable Web Applications # EJB Services # Clustering API # Singleton deployments # Singleton MSC services # Infinispan Subsystem # Groups Subsystem # mod_cluster Subsystem # Clustering and Domain Setup Walkthrough > Restructure High Availability Guide > ----------------------------------- > > Key: WFLY-12361 > URL: https://issues.jboss.org/browse/WFLY-12361 > Project: WildFly > Issue Type: Task > Components: Clustering > Affects Versions: 17.0.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > After migration to adoc, the headlines got converted incorrectly, while at this we want to reshuffle this to correspond more with: > # Introduction To High Availability Services > # Distributable Web Applications > # EJB Services > # Clustering API > # Singleton deployments > # Singleton MSC services > # Infinispan Subsystem > # JGroups Subsystem > # Singleton subsystem > # mod_cluster Subsystem > # Clustering and Domain Setup Walkthrough -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12361) Restructure High Availability Guide

by Radoslav Husar (Jira)

Radoslav Husar created WFLY-12361: ------------------------------------- Summary: Restructure High Availability Guide Key: WFLY-12361 URL: https://issues.jboss.org/browse/WFLY-12361 Project: WildFly Issue Type: Task Components: Clustering Affects Versions: 17.0.1.Final Reporter: Radoslav Husar Assignee: Radoslav Husar After migration to adoc, the headlines got converted incorrectly, while at this we want to reshuffle this to correspond more with: # Introduction To High Availability Services # Distributable Web Applications # EJB Services # Clustering API # Singleton deployments # Singleton MSC services # Infinispan Subsystem # Groups Subsystem # mod_cluster Subsystem # Clustering and Domain Setup Walkthrough -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4592) WildFly Core doesn't compile on Open JDK 14 anymore

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4592?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-4592: ------------------------------------------ JDK 14 issues can't be a Blocker for WildFly Core 10. > WildFly Core doesn't compile on Open JDK 14 anymore > --------------------------------------------------- > > Key: WFCORE-4592 > URL: https://issues.jboss.org/browse/WFCORE-4592 > Project: WildFly Core > Issue Type: Task > Components: Security > Environment: Since Open JDK 14 EA build 8 including > Reporter: Richard Opalka > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 10.0.0.Beta4 > > > [INFO] ------------------------------------------------------------- > [ERROR] COMPILATION ERROR : > [INFO] ------------------------------------------------------------- > [ERROR] /home/opalka/git/redhat/wildfly-core/domain-management/src/main/java/org/jboss/as/domain/management/security/JaasCallbackHandler.java:[224,51] cannot access java.security.acl.Group > class file for java.security.acl.Group not found > [INFO] 1 error > [INFO] ------------------------------------------------------------- -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4595) ControlledProcessState.State should expose whether a state means a running server

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4595: ---------------------------------------- Summary: ControlledProcessState.State should expose whether a state means a running server Key: WFCORE-4595 URL: https://issues.jboss.org/browse/WFCORE-4595 Project: WildFly Core Issue Type: Enhancement Components: Management Reporter: Brian Stansberry Assignee: Brian Stansberry Three of the ControlledProcessState.State enum values indicate the server is actually running, just with different relationships between the running configuration vs the persistent one. Add a boolean getter to distinguish those three from the others that indicate starting, stopping, stopped. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4594) Expose CoreProcessStateService functionality used by subsystems via a capability

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4594: ---------------------------------------- Summary: Expose CoreProcessStateService functionality used by subsystems via a capability Key: WFCORE-4594 URL: https://issues.jboss.org/browse/WFCORE-4594 Project: WildFly Core Issue Type: Enhancement Components: Management Reporter: Brian Stansberry Assignee: Brian Stansberry Subsystems are injecting CoreProcessStateService to track the process state, and perhaps more should as some are using graceful startup as a kind of trigger for beginning work, when the process reaching RUNNING state would be more appropriate. But: 1) they aren't using a capability for this wiring, because the kernel doesn't expose one 2) ControlledProcessStateService is not a clean API, as it exposes the MSC Service interface which should not be accessible to subsystems. So, add a ProcessStateNotifier interface, and expose it via a capability. Impl is still ControlledProcessStateService. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-917) Create Polarion Importer for Molecule Tests on Operator

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-917?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-917. ------------------------------------------- Resolution: Done > Create Polarion Importer for Molecule Tests on Operator > ------------------------------------------------------- > > Key: SWSQE-917 > URL: https://issues.jboss.org/browse/SWSQE-917 > Project: Kiali QE > Issue Type: Task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > Labels: infrastructure > > Create a new importer for molecule tests which are not covered by the existing polarion importers. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2320) FILE_PING.findMembers() optimizations

by Nick Sawadsky (Jira)

[ https://issues.jboss.org/browse/JGRP-2320?page=com.atlassian.jira.plugin.... ] Nick Sawadsky commented on JGRP-2320: ------------------------------------- Sounds good, thanks! > FILE_PING.findMembers() optimizations > ------------------------------------- > > Key: JGRP-2320 > URL: https://issues.jboss.org/browse/JGRP-2320 > Project: JGroups > Issue Type: Enhancement > Affects Versions: 3.6.16, 4.0.15 > Reporter: Nick Sawadsky > Assignee: Bela Ban > Priority: Minor > Fix For: 4.1.3 > > > Following on from JGRP-2288, a couple of possible optimizations/improvements to {{FILE_PING.findMembers()}} were identified. > 1. After the initial call to {{readAll()}}, some corrective steps are taken if the local node address was not returned by {{readAll()}}. However, in the case where {{findMembers()}} is invoked by {{TP.fetchResponsesFromDiscoveryProtocol()}}, it is normal if the local node address is not returned, since the {{readAll()}} responses are filtered based on the {{members}} parameter. > To avoid unnecessary writes to the file or cloud store, it would be good to add some checks based on whether {{members}} is null or not. For example, the calls to {{write()}} and {{writeAll()}} should probably not occur unless {{members}} is null. > 2. In the call to {{sendDiscoveryResponse()}}, the last parameter is always {{false}}. However, it seems possible for a coordinator to get to this point in some edge cases. Though I haven't been able to identify any clear bugs that this would lead to, it might be better to pass {{is_coord}} as the last parameter. -- 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 Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1819?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on ELY-1819: --------------------------------------- At the very least maybe Consumer<HttpServerScopes> could be sufficient. > 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] (WFLY-12360) Upgrade org.jboss.spec.javax.el from 1.0.13.Final to 2.0.0.Final

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-12360?page=com.atlassian.jira.plugin... ] Scott Marlow updated WFLY-12360: -------------------------------- Fix Version/s: 18.0.0.Beta1 > Upgrade org.jboss.spec.javax.el from 1.0.13.Final to 2.0.0.Final > ---------------------------------------------------------------- > > Key: WFLY-12360 > URL: https://issues.jboss.org/browse/WFLY-12360 > Project: WildFly > Issue Type: Sub-task > Components: EE > Reporter: Scott Marlow > Assignee: Scott Marlow > Priority: Critical > Fix For: 18.0.0.Beta1 > > > JBoss Jakarta Expression Language API: > https://github.com/jboss/jboss-jakarta-el-api_spec -- 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