June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4227) Kubernetes configuration for remote debug

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4227?page=com.atlassian.jira.plugi... ] Massimiliano Dessi commented on DROOLS-4227: -------------------------------------------- https://github.com/desmax74/openshift-hacep/commit/ca7f465cf2084209d8814a... > Kubernetes configuration for remote debug > ----------------------------------------- > > Key: DROOLS-4227 > URL: https://issues.jboss.org/browse/DROOLS-4227 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4227) Kubernetes configuration for remote debug

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4227?page=com.atlassian.jira.plugi... ] Massimiliano Dessi resolved DROOLS-4227. ---------------------------------------- Resolution: Done > Kubernetes configuration for remote debug > ----------------------------------------- > > Key: DROOLS-4227 > URL: https://issues.jboss.org/browse/DROOLS-4227 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12232) socket-binding "jgroups-tcp-fd" for FD_SOCK is used for UPD stack

by Vlasta Ramik (Jira)

Vlasta Ramik created WFLY-12232: ----------------------------------- Summary: socket-binding "jgroups-tcp-fd" for FD_SOCK is used for UPD stack Key: WFLY-12232 URL: https://issues.jboss.org/browse/WFLY-12232 Project: WildFly Issue Type: Bug Affects Versions: 17.0.0.Final Reporter: Vlasta Ramik Assignee: Brian Stansberry There are switched names of socket bindings in jgroups.xml * https://github.com/wildfly/wildfly/commit/5ee199b7ecd3166a5afdc97425af412... * https://github.com/wildfly/wildfly/commit/5ee199b7ecd3166a5afdc97425af412... when legacy build system is used, e.g. like [here|https://github.com/keycloak/keycloak/blob/master/distribution/featur...] it ends with switched values than in standalone-ha.xml from wildfly17 dist -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4226) Enable a fast forward system to skip already processed events

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4226?page=com.atlassian.jira.plugi... ] Massimiliano Dessi updated DROOLS-4226: --------------------------------------- Description: Using the identifier data of the last processed event on the Control topic , we need to skip the event on the topic from the head without procesing and start the work on the events only when the last processed event is found on the events topic > Enable a fast forward system to skip already processed events > ------------------------------------------------------------- > > Key: DROOLS-4226 > URL: https://issues.jboss.org/browse/DROOLS-4226 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > > Using the identifier data of the last processed event on the Control topic , we need to skip the event on the topic from the head without procesing and start the work on the events only when the last processed event is found on the events topic -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4226) Enable a fast forward system to skip already processed events

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4226?page=com.atlassian.jira.plugi... ] Massimiliano Dessi resolved DROOLS-4226. ---------------------------------------- Resolution: Done > Enable a fast forward system to skip already processed events > ------------------------------------------------------------- > > Key: DROOLS-4226 > URL: https://issues.jboss.org/browse/DROOLS-4226 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > > Using the identifier data of the last processed event on the Control topic , we need to skip the event on the topic from the head without procesing and start the work on the events only when the last processed event is found on the events topic -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12233) Upgrade Hibernate ORM from 5.3.10 to 5.3.11

by Martin Stefanko (Jira)

Martin Stefanko created WFLY-12233: -------------------------------------- Summary: Upgrade Hibernate ORM from 5.3.10 to 5.3.11 Key: WFLY-12233 URL: https://issues.jboss.org/browse/WFLY-12233 Project: WildFly Issue Type: Component Upgrade Components: JPA / Hibernate Affects Versions: 17.0.0.Final Reporter: Martin Stefanko Assignee: Scott Marlow -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4226) Enable a fast forward system to skip already processed events

by Massimiliano Dessi (Jira)

Massimiliano Dessi created DROOLS-4226: ------------------------------------------ Summary: Enable a fast forward system to skip already processed events Key: DROOLS-4226 URL: https://issues.jboss.org/browse/DROOLS-4226 Project: Drools Issue Type: Task Reporter: Massimiliano Dessi Assignee: Massimiliano Dessi -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4225) Create an API to scroll events received on the topics

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4225?page=com.atlassian.jira.plugi... ] Massimiliano Dessi resolved DROOLS-4225. ---------------------------------------- Resolution: Done > Create an API to scroll events received on the topics > ----------------------------------------------------- > > Key: DROOLS-4225 > URL: https://issues.jboss.org/browse/DROOLS-4225 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4225) Create an API to scroll events received on the topics

by Massimiliano Dessi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4225?page=com.atlassian.jira.plugi... ] Massimiliano Dessi commented on DROOLS-4225: -------------------------------------------- https://github.com/desmax74/openshift-hacep/commit/d57a8ca52b2aa6d266e484... > Create an API to scroll events received on the topics > ----------------------------------------------------- > > Key: DROOLS-4225 > URL: https://issues.jboss.org/browse/DROOLS-4225 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4213) [DMN Designer] Search feature - Define search architectural approach

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4213?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-4213: ------------------------------------ Description: This JIRAs refers to the discussions for different implementation approaches that can be adopted for supporting GDT editor and DMN editor. With this JIRA done, two initial implementations will be triggered: - https://issues.jboss.org/browse/DROOLS-4212 (DMN graph PoC) - https://issues.jboss.org/browse/DROOLS-4211 (GDT PoC) --- h5. Definitions: All GDT cells, DRG Elements, and any other searchable element would need to implement this interface: {code} interface Searchable { boolean matches(final String text) Command onFound() } {code} In the UI, each editor instance would have an instance of {{SearchBarComponent.java}} (..and a {{SearchBarComponentView.java}} and {{SearchBarComponentView.html}}). This simple UI component would call the editor index, that would have all {{Searchable}} elements. When a given component has the desired text, the respective command would be executed. --- h5. Questions to answer: - How to index all Searchable items? - How to keep index updated? was: This JIRAs refers to the discussions for different implementation approaches that can be adopted for supporting GDT editor and DMN editor. With this JIRA done, two initial implementations will be triggered: - https://issues.jboss.org/browse/DROOLS-4212 (DMN graph PoC) - https://issues.jboss.org/browse/DROOLS-4211 (GDT PoC) --- Definitions: All GDT cells, DRG Elements, and any other searchable element would need to implement this interface: {code} interface Searchable { boolean matches(final String text) Command onFound() } {code} In the UI, each editor instance would have an instance of {{SearchBarComponent.java}} (..and a {{SearchBarComponentView.java}} and {{SearchBarComponentView.html}}). This simple UI component would call the editor index, that would have all {{Searchable}} elements. When a given component has the desired text, the respective command would be executed. --- Questions to answer: - How to index all Searchable items? - How to keep index updated? > [DMN Designer] Search feature - Define search architectural approach > -------------------------------------------------------------------- > > Key: DROOLS-4213 > URL: https://issues.jboss.org/browse/DROOLS-4213 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > This JIRAs refers to the discussions for different implementation approaches that can be adopted for supporting GDT editor and DMN editor. > With this JIRA done, two initial implementations will be triggered: > - https://issues.jboss.org/browse/DROOLS-4212 (DMN graph PoC) > - https://issues.jboss.org/browse/DROOLS-4211 (GDT PoC) > --- > h5. Definitions: > All GDT cells, DRG Elements, and any other searchable element would need to implement this interface: > {code} > interface Searchable { > boolean matches(final String text) > Command onFound() > } > {code} > In the UI, each editor instance would have an instance of {{SearchBarComponent.java}} (..and a {{SearchBarComponentView.java}} and {{SearchBarComponentView.html}}). This simple UI component would call the editor index, that would have all {{Searchable}} elements. When a given component has the desired text, the respective command would be executed. > --- > h5. Questions to answer: > - How to index all Searchable items? > - How to keep index updated? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 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 June 2019