March 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2423) [DMN Designer] Clear command caches context entries

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2423?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2423: -------------------------------- Description: This issue was spotted during review of DROOLS-2392, however relation is not probable between both. If user clears the top level context entry and then select same context entry exactly the same context entry will appear. There should appear context entry with default values. h2. Acceptance test # check scenario described in [PR comments|https://github.com/kiegroup/kie-wb-common/pull/1548] # check scenario from DROOLS-2424 # TO DO was: This issue was spotted during review of DROOLS-2392, however relation is not probable between both. If user clears the top level context entry and then select same context entry exactly the same context entry will appear. There should appear context entry with default values. h2. Acceptance test # Test scenario described in [PR comments|https://github.com/kiegroup/kie-wb-common/pull/1548] # TO DO > [DMN Designer] Clear command caches context entries > --------------------------------------------------- > > Key: DROOLS-2423 > URL: https://issues.jboss.org/browse/DROOLS-2423 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Attachments: Screenshot from 2018-03-27 11-31-01.png, Screenshot from 2018-03-27 11-31-34.png, Screenshot from 2018-03-27 11-32-52.png > > > This issue was spotted during review of DROOLS-2392, however relation is not probable between both. > If user clears the top level context entry and then select same context entry exactly the same context entry will appear. There should appear context entry with default values. > h2. Acceptance test > # check scenario described in [PR comments|https://github.com/kiegroup/kie-wb-common/pull/1548] > # check scenario from DROOLS-2424 > # TO DO -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2423) [DMN Designer] Clear command caches context entries

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2423?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2423: -------------------------------- Description: This issue was spotted during review of DROOLS-2392, however relation is not probable between both. If user clears the top level context entry and then select same context entry exactly the same context entry will appear. There should appear context entry with default values. h2. Acceptance test # Test scenario described in [PR comments|https://github.com/kiegroup/kie-wb-common/pull/1548] # TO DO was: This issue was spotted during review of DROOLS-2392, however relation is not probable between both. If user clears the top level context entry and then select same context entry exactly the same context entry will appear. There should appear context entry with default values. > [DMN Designer] Clear command caches context entries > --------------------------------------------------- > > Key: DROOLS-2423 > URL: https://issues.jboss.org/browse/DROOLS-2423 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Attachments: Screenshot from 2018-03-27 11-31-01.png, Screenshot from 2018-03-27 11-31-34.png, Screenshot from 2018-03-27 11-32-52.png > > > This issue was spotted during review of DROOLS-2392, however relation is not probable between both. > If user clears the top level context entry and then select same context entry exactly the same context entry will appear. There should appear context entry with default values. > h2. Acceptance test > # Test scenario described in [PR comments|https://github.com/kiegroup/kie-wb-common/pull/1548] > # TO DO -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2432) [DMN Designer] Back to from DRD doesn't select proper element in DRG

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2432?page=com.atlassian.jira.plugi... ] Michael Anstis reassigned DROOLS-2432: -------------------------------------- Assignee: Guilherme Carreiro (was: Michael Anstis) > [DMN Designer] Back to from DRD doesn't select proper element in DRG > -------------------------------------------------------------------- > > Key: DROOLS-2432 > URL: https://issues.jboss.org/browse/DROOLS-2432 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Minor > > If user navigates back from DRD, the selection in DRG is not updated. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2436) [DMN Designer] Always open the same diagram

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2436?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2436: ----------------------------------- Sprint: 2018 Week 13-14 > [DMN Designer] Always open the same diagram > ------------------------------------------- > > Key: DROOLS-2436 > URL: https://issues.jboss.org/browse/DROOLS-2436 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > > User is unable to open two different diagrams. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2435) [DMN Designer] Active entries highlight between navigation

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2435?page=com.atlassian.jira.plugi... ] Michael Anstis reassigned DROOLS-2435: -------------------------------------- Assignee: Guilherme Carreiro (was: Michael Anstis) > [DMN Designer] Active entries highlight between navigation > ---------------------------------------------------------- > > Key: DROOLS-2435 > URL: https://issues.jboss.org/browse/DROOLS-2435 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Minor > > If user edits two decision nodes concurrently, then active entries are not highlighted correctly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1968) [DMN Editor] Canvas Panning

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1968?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-1968: -------------------------------- Labels: Stunner (was: reported-by-qe) > [DMN Editor] Canvas Panning > --------------------------- > > Key: DROOLS-1968 > URL: https://issues.jboss.org/browse/DROOLS-1968 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Optional > Labels: Stunner > > The DMN Editor should support panning of the DRD. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2436) [DMN Designer] Always open the same diagram

by Jozef Marko (JIRA)

Jozef Marko created DROOLS-2436: ----------------------------------- Summary: [DMN Designer] Always open the same diagram Key: DROOLS-2436 URL: https://issues.jboss.org/browse/DROOLS-2436 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.8.0.Final Reporter: Jozef Marko Assignee: Michael Anstis Priority: Blocker User is unable to open two different diagrams. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3658) Security context propagation using Elytron API doesn't work for EJB to protected Servlet scenario

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3658?page=com.atlassian.jira.plugi... ] Stuart Douglas reopened WFCORE-3658: ------------------------------------ > Security context propagation using Elytron API doesn't work for EJB to protected Servlet scenario > ------------------------------------------------------------------------------------------------- > > Key: WFCORE-3658 > URL: https://issues.jboss.org/browse/WFCORE-3658 > Project: WildFly Core > Issue Type: Enhancement > Components: Security > Reporter: Ondrej Lukas > Assignee: Jan Kalina > Priority: Critical > Fix For: 5.0.0.Alpha1 > > > One of the scenarios which are expected to work in Elytron is a Security context propagation from a protected EJB to a protected Servlet using HttpUrlConnection (details in RFE EAP7-284). > The scenario doesn't work for me. My configuration: > {noformat} > EJB client -> protected EJB on server-1 -> protected Servlet on server-2 (BASIC authn) > {noformat} > The EJB contains following code: > {code:java} > final Callable<String> callable = () -> { > URLConnection conn = url.openConnection(); > conn.connect(); > try (InputStream is = conn.getInputStream()) { > return IOUtils.toString(is, StandardCharsets.UTF_8); > } > }; > AuthenticationContext.empty().with(MatchRule.ALL, AuthenticationConfiguration.empty() > .useForwardedIdentity(SecurityDomain.getCurrent()) > .setSaslMechanismSelector(SaslMechanismSelector.ALL)) > .runCallable(callable); > {code} > The server-2 returns 401: > {noformat} > java.io.IOException: Server returned HTTP response code: 401 for URL: http://127.0.0.1:8180/seccontext-server2/whoAmI > at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1876) > at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474) > at org.wildfly.test.manual.elytron.seccontext.EntryBean.lambda$readUrl$1(EntryBean.java:69) > {noformat} > There is still a chance, the problem is in the scenario configuration, but the documentation is silent about this topic. > The problem could be in a missing integration of ElytronAuthenticator within the AuthenticationContext. I don't see it used when I debug the scenario. When I register the authenticator manually, I see another problem which will be reported in a separate JIRA. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6803) Add multi-server support to mod_cluster

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6803?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-6803: -------------------------------------- Opened EAP7-977 and reclassified as feature request because this is quite a change and will require proper QE testing. > Add multi-server support to mod_cluster > --------------------------------------- > > Key: WFLY-6803 > URL: https://issues.jboss.org/browse/WFLY-6803 > Project: WildFly > Issue Type: Feature Request > Components: mod_cluster > Affects Versions: 10.0.0.Final > Reporter: Paul Ferraro > Assignee: Radoslav Husar > > Currently, mod_cluster subsystem supports only a single configuration, which references the default undertow server. However, Undertow supports multiple servers, and exposes a distinct route capability per server (see WFLY-6778). mod_cluster should therefore support multiple "profiles", where each profile references a specific undertow server. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6803) Add multi-server support to mod_cluster

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6803?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-6803: --------------------------------- Issue Type: Feature Request (was: Enhancement) > Add multi-server support to mod_cluster > --------------------------------------- > > Key: WFLY-6803 > URL: https://issues.jboss.org/browse/WFLY-6803 > Project: WildFly > Issue Type: Feature Request > Components: mod_cluster > Affects Versions: 10.0.0.Final > Reporter: Paul Ferraro > Assignee: Radoslav Husar > > Currently, mod_cluster subsystem supports only a single configuration, which references the default undertow server. However, Undertow supports multiple servers, and exposes a distinct route capability per server (see WFLY-6778). mod_cluster should therefore support multiple "profiles", where each profile references a specific undertow server. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 March 2018