July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2744) [DMN Designer] Global diagram properties

by Roger Martínez (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2744?page=com.atlassian.jira.plugi... ] Roger Martínez commented on DROOLS-2744: ---------------------------------------- Hey [~jomarko] Those properties were disabled on BPMN, not really sure if you need them on DMN. The idea is to enable some of those for some kind of BPMN nodes sooner than later, but there is still no plan to work on that side, at least, for BPMN, yet. > [DMN Designer] Global diagram properties > ---------------------------------------- > > Key: DROOLS-2744 > URL: https://issues.jboss.org/browse/DROOLS-2744 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.9.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > > The global diagram properties for DMN diagram contains sections settings for: > - dimensions > - backround > - font > However change of any of them (globally, for the whole diagram) doesn't seem to affect particular nodes somehow. We should hide these settings or implement the logic that would affect all nodes in diagram by change on this place. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3967) Upgrade to Galleon and WildFly Galleon Plugins 2.0.0.Alpha4

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created WFCORE-3967: ----------------------------------------- Summary: Upgrade to Galleon and WildFly Galleon Plugins 2.0.0.Alpha4 Key: WFCORE-3967 URL: https://issues.jboss.org/browse/WFCORE-3967 Project: WildFly Core Issue Type: Component Upgrade Components: Build System Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Galleon 2.x is the version branch which is going to be exposed as a supported external tool for provisioning, updates and patching. The main difference to Galleon 1.x that it brings into WildFly build process is it is based on different format for expressing feature-pack locations than Maven coordinates and uses a resolution mechanism to resolve feature-pack artifacts, which is the base for version updates and patches discovery. There is still a way to provide Maven coordinates for feature-packs and avoid going through the default feature-pack resolution mechanism. Another feature it brings in and which appears in wildfly feature-pack configs is proper transitive dependency customizations. The equivalent change for WFLY is WFLY-10703 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10711) Implement Health Check so that it can be consumed by OpenShift Console

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10711?page=com.atlassian.jira.plugin... ] Brian Stansberry moved EAP7-1056 to WFLY-10711: ----------------------------------------------- Project: WildFly (was: EAP 7 Planning Pilot) Key: WFLY-10711 (was: EAP7-1056) Issue Type: Feature Request (was: Requirement) Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0) Component/s: (was: OpenShift) Jirban PT Pre-Checked (PC): (was: TODO) Target Release: (was: 7.2.0.GA) Jirban PT Community Docs (CD): (was: TODO) Jirban PT Product Docs (PD): (was: New) Jirban PT Test Dev (TD): (was: TODO) Jirban PT Docs Analysis (DA): (was: TODO) Jirban PT Test Plan (TP): (was: TODO) Jirban PT Analysis Document (AD): (was: TODO) > Implement Health Check so that it can be consumed by OpenShift Console > ---------------------------------------------------------------------- > > Key: WFLY-10711 > URL: https://issues.jboss.org/browse/WFLY-10711 > Project: WildFly > Issue Type: Feature Request > Reporter: Bilge Ozpeynirci > Assignee: Jeff Mesnil > Labels: OS_Observability > > Implement Health Check so that it can be consumed by OpenShift Console > This should be implemented in manner that is consistent with WildFly Swarm i.e. MicroProfile specifications where applicable. > This requirement can be delivered as Technology Preview for WF 14. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10710) Wildfly keycloak and application configuration | how to resolve this error

by Lilly rose (JIRA)

Lilly rose created WFLY-10710: --------------------------------- Summary: Wildfly keycloak and application configuration | how to resolve this error Key: WFLY-10710 URL: https://issues.jboss.org/browse/WFLY-10710 Project: WildFly Issue Type: Bug Environment: wildfly 11 final , Reporter: Lilly rose Assignee: Jason Greene ESC[0mESC[31m16:36:59,379 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /sample/: java.lang.NullPointerException at java.lang.String.contains(String.java:2133) at org.keycloak.adapters.saml.elytron.KeycloakHttpServerAuthenticationMechanism.evaluateRequest(KeycloakHttpServerAuthenticationMechanism.java:82) at org.wildfly.security.http.util.SetMechanismInformationMechanismFactory$1.evaluateRequest(SetMechanismInformationMechanismFactory.java:114) at org.wildfly.security.http.util.SecurityIdentityServerMechanismFactory$1.evaluateRequest(SecurityIdentityServerMechanismFactory.java:77) at org.wildfly.security.http.HttpAuthenticator$AuthenticationExchange.authenticate(HttpAuthenticator.java:115) at org.wildfly.security.http.HttpAuthenticator$AuthenticationExchange.access$100(HttpAuthenticator.java:94) at org.wildfly.security.http.HttpAuthenticator.authenticate(HttpAuthenticator.java:78) at org.wildfly.elytron.web.undertow.server.SecurityContextImpl.authenticate(SecurityContextImpl.java:100) at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292) at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138) at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135) at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48) at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10709) Expose "Tracing" information so that it can be consumed by OpenShift Console

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10709?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-10709: ------------------------------------ Description: Expose Tracing Data so that it can be consumed by OpenShift Console This should be implemented in manner that is consistent with WildFly Swarm i.e. MicroProfile specifications where applicable. This requirement can be delivered as Technology Preview for WF 14. was: Expose EAP Tracing Data so that it can be consumed by OpenShift Console This should be implemented in manner that is consistent with WildFly Swarm i.e. MicroProfile specifications where applicable. This requirement can be delivered as Technology Preview for EAP 7.2 > Expose "Tracing" information so that it can be consumed by OpenShift Console > ---------------------------------------------------------------------------- > > Key: WFLY-10709 > URL: https://issues.jboss.org/browse/WFLY-10709 > Project: WildFly > Issue Type: Feature Request > Reporter: Bilge Ozpeynirci > Assignee: Juraci Paixão Kröhling > Labels: OS_Observability > > Expose Tracing Data so that it can be consumed by OpenShift Console > This should be implemented in manner that is consistent with WildFly Swarm i.e. MicroProfile specifications where applicable. > This requirement can be delivered as Technology Preview for WF 14. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10709) Expose "Tracing" information so that it can be consumed by OpenShift Console

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10709?page=com.atlassian.jira.plugin... ] Brian Stansberry moved EAP7-1053 to WFLY-10709: ----------------------------------------------- Project: WildFly (was: EAP 7 Planning Pilot) Key: WFLY-10709 (was: EAP7-1053) Issue Type: Feature Request (was: Requirement) Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0) Component/s: (was: OpenShift) Jirban PT Pre-Checked (PC): (was: TODO) Target Release: (was: 7.2.0.GA) Jirban PT Community Docs (CD): (was: TODO) Jirban PT Product Docs (PD): (was: New) Jirban PT Test Dev (TD): (was: TODO) Jirban PT Docs Analysis (DA): (was: TODO) Jirban PT Test Plan (TP): (was: TODO) Jirban PT Analysis Document (AD): (was: TODO) > Expose "Tracing" information so that it can be consumed by OpenShift Console > ---------------------------------------------------------------------------- > > Key: WFLY-10709 > URL: https://issues.jboss.org/browse/WFLY-10709 > Project: WildFly > Issue Type: Feature Request > Reporter: Bilge Ozpeynirci > Assignee: Brian Stansberry > Labels: OS_Observability > > Expose EAP Tracing Data so that it can be consumed by OpenShift Console > This should be implemented in manner that is consistent with WildFly Swarm i.e. MicroProfile specifications where applicable. > This requirement can be delivered as Technology Preview for EAP 7.2 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10709) Expose "Tracing" information so that it can be consumed by OpenShift Console

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10709?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-10709: --------------------------------------- Assignee: Juraci Paixão Kröhling (was: Brian Stansberry) > Expose "Tracing" information so that it can be consumed by OpenShift Console > ---------------------------------------------------------------------------- > > Key: WFLY-10709 > URL: https://issues.jboss.org/browse/WFLY-10709 > Project: WildFly > Issue Type: Feature Request > Reporter: Bilge Ozpeynirci > Assignee: Juraci Paixão Kröhling > Labels: OS_Observability > > Expose EAP Tracing Data so that it can be consumed by OpenShift Console > This should be implemented in manner that is consistent with WildFly Swarm i.e. MicroProfile specifications where applicable. > This requirement can be delivered as Technology Preview for EAP 7.2 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2755) [DMN Designer] Error when the user switches between DMN files

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2755?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2755: -------------------------------- Affects Version/s: 7.9.0.Final > [DMN Designer] Error when the user switches between DMN files > ------------------------------------------------------------- > > Key: DROOLS-2755 > URL: https://issues.jboss.org/browse/DROOLS-2755 > Project: Drools > Issue Type: Bug > Affects Versions: 7.9.0.Final > Reporter: Guilherme Carreiro > Assignee: Michael Anstis > Labels: drools-tools > Attachments: demo.gif > > > When the user switches between DMN files, the following error happens: > !demo.gif|thumbnail! > It's an intermittent problem, therefore the steps to reproduce the bug (showed in the GIF) don't propagate the error every time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2755) [DMN Designer] Error when the user switches between DMN files

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2755?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2755: -------------------------------- Labels: drools-tools (was: ) > [DMN Designer] Error when the user switches between DMN files > ------------------------------------------------------------- > > Key: DROOLS-2755 > URL: https://issues.jboss.org/browse/DROOLS-2755 > Project: Drools > Issue Type: Bug > Reporter: Guilherme Carreiro > Assignee: Michael Anstis > Labels: drools-tools > Attachments: demo.gif > > > When the user switches between DMN files, the following error happens: > !demo.gif|thumbnail! > It's an intermittent problem, therefore the steps to reproduce the bug (showed in the GIF) don't propagate the error every time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2755) [DMN Designer] Error when the user switches between DMN files

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2755?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2755: -------------------------------- Tester: Jozef Marko > [DMN Designer] Error when the user switches between DMN files > ------------------------------------------------------------- > > Key: DROOLS-2755 > URL: https://issues.jboss.org/browse/DROOLS-2755 > Project: Drools > Issue Type: Bug > Reporter: Guilherme Carreiro > Assignee: Michael Anstis > Labels: drools-tools > Attachments: demo.gif > > > When the user switches between DMN files, the following error happens: > !demo.gif|thumbnail! > It's an intermittent problem, therefore the steps to reproduce the bug (showed in the GIF) don't propagate the error every time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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 July 2018