October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-192) Sync eap CRD with wildfly CRD

by Petr Kremensky (Jira)

[ https://issues.jboss.org/browse/WFWIP-192?page=com.atlassian.jira.plugin.... ] Petr Kremensky updated WFWIP-192: --------------------------------- Labels: operator (was: ) > Sync eap CRD with wildfly CRD > ----------------------------- > > Key: WFWIP-192 > URL: https://issues.jboss.org/browse/WFWIP-192 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Major > Labels: operator > > Comparing wildfly and eap CRD revealed differences > {code} > wget https://raw.githubusercontent.com/wildfly/wildfly-operator/master/deploy/... -O wildfly_operator_crd > wget https://raw.githubusercontent.com/jbossas/eap-operator-packaging/prototyp... -O eap_operator_crd > diff wildfly_operator_crd eap_operator_crd > {code} > {code} > 36,37d35 > < disableHTTPRoute: > < type: boolean > 50,53d47 > < sessionAffinity: > < description: SessionAffinity defines if connections from the same client > < ip are passed to the same WildFlyServer instance/pod each time > < type: boolean > 79,82d72 > < hosts: > < items: > < type: string > < type: array > 94a85,86 > > required: > > - pods > {code} > Please sync so we can test against. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-219) Operator is missing node/pod affinity setting

by Petr Kremensky (Jira)

[ https://issues.jboss.org/browse/WFWIP-219?page=com.atlassian.jira.plugin.... ] Petr Kremensky updated WFWIP-219: --------------------------------- Labels: operator (was: ) > Operator is missing node/pod affinity setting > --------------------------------------------- > > Key: WFWIP-219 > URL: https://issues.jboss.org/browse/WFWIP-219 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Critical > Labels: operator > > As a user I am able to configure pod/node affinity > {code:yaml} > affinity: > nodeAffinity: > preferredDuringSchedulingIgnoredDuringExecution: > requiredDuringSchedulingIgnoredDuringExecution: > podAffinity: > preferredDuringSchedulingIgnoredDuringExecution: > requiredDuringSchedulingIgnoredDuringExecution: > podAntiAffinity: > preferredDuringSchedulingIgnoredDuringExecution: > requiredDuringSchedulingIgnoredDuringExecution: > nodeName: > nodeSelector: > schedulerName > tolerations" > {code} > [1] https://docs.openshift.com/container-platform/3.11/rest_api/apis-apps/v1b... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4574) Scenario test: UX to add an expression-based value.

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4574?page=com.atlassian.jira.plugi... ] Elizabeth Clayton edited comment on DROOLS-4574 at 10/1/19 8:23 AM: -------------------------------------------------------------------- [~danielezonca] Just something in the right-panel UI to help the user to understand that they can A) select the parent, and that when they do it will B) set the field as an expression. - And I know it's out of scope, but for a future consideration - in DMN we're repurposing the DO selector tree widget and adding a checkbox to the parent DO's. See: https://issues.jboss.org/browse/DROOLS-4481. I believe [~karreiro] will be implementing it. was (Author: uxdlc): [~danielezonca] Just something in the right-panel UI to help the user to understand that they can A) select the parent, and that when they do it will B) set the field as an expression. - And I know it's out of scope, but for a future consideration - in DMN we're repurposing the DO selector tree widget and adding a checkbox to the parent DO's. See: https://issues.jboss.org/browse/DROOLS-4481. I believe [~karreiro] will be implementing it. !Screen Shot 2019-10-01 at 8.13.41 AM.png|thumbnail! > Scenario test: UX to add an expression-based value. > ---------------------------------------------------- > > Key: DROOLS-4574 > URL: https://issues.jboss.org/browse/DROOLS-4574 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam > > As a technical/advanced user (Cameron), I want to be able to input expression-based values in scenario given/expect row cells, so that I can define inputs for complex objects and logic. > Note: Syntax highlighting and etc., are out of scope. Refer to: https://issues.jboss.org/browse/DROOLS-3514 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4574) Scenario test: UX to add an expression-based value.

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4574?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4574: -------------------------------------- Attachment: (was: Screen Shot 2019-10-01 at 8.13.41 AM.png) > Scenario test: UX to add an expression-based value. > ---------------------------------------------------- > > Key: DROOLS-4574 > URL: https://issues.jboss.org/browse/DROOLS-4574 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam > > As a technical/advanced user (Cameron), I want to be able to input expression-based values in scenario given/expect row cells, so that I can define inputs for complex objects and logic. > Note: Syntax highlighting and etc., are out of scope. Refer to: https://issues.jboss.org/browse/DROOLS-3514 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12573) Upgrade picketbox from 5.0.3.Final-redhat-00004 to 5.0.3.Final-redhat-00005

by Ilia Vassilev (Jira)

[ https://issues.jboss.org/browse/WFLY-12573?page=com.atlassian.jira.plugin... ] Ilia Vassilev closed WFLY-12573. -------------------------------- Release Notes Text: duplicate of WFCORE-4653 Resolution: Done > Upgrade picketbox from 5.0.3.Final-redhat-00004 to 5.0.3.Final-redhat-00005 > --------------------------------------------------------------------------- > > Key: WFLY-12573 > URL: https://issues.jboss.org/browse/WFLY-12573 > Project: WildFly > Issue Type: Component Upgrade > Affects Versions: 18.0.0.Beta1 > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12617) org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL flag ignored when WARs are embedded in EAR

by Angel Olle Blazquez (Jira)

Angel Olle Blazquez created WFLY-12617: ------------------------------------------ Summary: org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL flag ignored when WARs are embedded in EAR Key: WFLY-12617 URL: https://issues.jboss.org/browse/WFLY-12617 Project: WildFly Issue Type: Bug Components: JSF Affects Versions: 15.0.0.Final, 16.0.0.Final, 17.0.0.Final, 18.0.0.Beta1 Reporter: Angel Olle Blazquez Assignee: Farah Juma Due to changes indroduced to fix bug WFLY-10796 it is no longer possible to configure wars embedded in ear to bundle jsf implementation. Changes made in file JSFDependencyProcessor.java in commit 40f72548985a9f5ca31317b01a4a0ce09ee759aa From: {code} final DeploymentUnit tl = deploymentUnit.getParent() == null ? deploymentUnit : deploymentUnit.getParent(); String jsfVersion = JsfVersionMarker.getVersion(tl); {code} To: {code} String jsfVersion = JsfVersionMarker.getVersion(deploymentUnit); {code} modified the way jsf version is aquired. Before the change it was always taken from top level deployment. After it is taken directly from scanned deployment unit without searching in parent. Unfortunately there was no matching change in a way context params from web.xml are processed in JSFVersionProcessor: {code} final DeploymentUnit topLevelDeployment = deploymentUnit.getParent() == null ? deploymentUnit : deploymentUnit.getParent(); final WarMetaData metaData = deploymentUnit.getAttachment(WarMetaData.ATTACHMENT_KEY); List<ParamValueMetaData> contextParams = new ArrayList<ParamValueMetaData>(); if ((metaData.getWebMetaData() != null) && (metaData.getWebMetaData().getContextParams() != null)) { contextParams.addAll(metaData.getWebMetaData().getContextParams()); } for (final ParamValueMetaData param : contextParams) { if ((param.getParamName().equals(WAR_BUNDLES_JSF_IMPL_PARAM) && (param.getParamValue() != null) && (param.getParamValue().toLowerCase(Locale.ENGLISH).equals("true")))) { JsfVersionMarker.setVersion(topLevelDeployment, JsfVersionMarker.WAR_BUNDLES_JSF_IMPL); break; // WAR_BUNDLES_JSF_IMPL always wins } if (param.getParamName().equals(JSF_CONFIG_NAME_PARAM)) { JsfVersionMarker.setVersion(topLevelDeployment, param.getParamValue()); break; } } {code} So the information about org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL flag is only set in top level deployment unit. This causes Mojarra-2.0 to be returned as jsf version during checks in JSFDependencyProcessor for embedded wars and leads to initialization of default mojarra implementation before bundled implementation is processed. As both implementations are loaded class conflicts occur and it is not possible to properly initialize jsf. In case of myfaces this leads to below error: {code} 2019-09-16 10:46:23,405 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 86) MSC000001: Failed to start service jboss.deployment.subunit."xxx.ear"."yyy.war".undertow-deployment: org.jboss.msc.service.StartException in service jboss.deployment.subunit."xxx.ear"."yyy.war".undertow-deployment: java.lang.RuntimeException: java.lang.IllegalStateException: Could not find backup for factory javax.faces.application.ApplicationFactory. at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:81) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) at java.lang.Thread.run(Thread.java:748) at org.jboss.threads.JBossThread.run(JBossThread.java:485) Caused by: java.lang.RuntimeException: java.lang.IllegalStateException: Could not find backup for factory javax.faces.application.ApplicationFactory. at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:252) at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:96) at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:78) ... 8 more Caused by: java.lang.IllegalStateException: Could not find backup for factory javax.faces.application.ApplicationFactory. at javax.faces.FactoryFinderInstance.notNullFactory(FactoryFinderInstance.java:524) at javax.faces.FactoryFinderInstance.getFactory(FactoryFinderInstance.java:207) at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:279) at org.apache.myfaces.context.servlet.FacesContextImplBase.getApplication(FacesContextImplBase.java:159) at org.apache.myfaces.context.servlet.FacesContextImplBase.getELContext(FacesContextImplBase.java:210) at javax.faces.component.UIViewRoot.setLocale(UIViewRoot.java:1602) at org.apache.myfaces.webapp.AbstractFacesInitializer._createFacesContext(AbstractFacesInitializer.java:477) at org.apache.myfaces.webapp.AbstractFacesInitializer.initStartupFacesContext(AbstractFacesInitializer.java:449) at org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:113) at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187) at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:216) at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:185) at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42) at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502) at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:250) ... 10 more {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4574) Scenario test: UX to add an expression-based value.

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4574?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-4574: ------------------------------------------- [~danielezonca] Just something in the right-panel UI to help the user to understand that they can A) select the parent, and that when they do it will B) set the field as an expression. - And I know it's out of scope, but for a future consideration - in DMN we're repurposing the DO selector tree widget and adding a checkbox to the parent DO's. See: https://issues.jboss.org/browse/DROOLS-4481. I believe [~karreiro] will be implementing it. !Screen Shot 2019-10-01 at 8.13.41 AM.png|thumbnail! > Scenario test: UX to add an expression-based value. > ---------------------------------------------------- > > Key: DROOLS-4574 > URL: https://issues.jboss.org/browse/DROOLS-4574 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam > Attachments: Screen Shot 2019-10-01 at 8.13.41 AM.png > > > As a technical/advanced user (Cameron), I want to be able to input expression-based values in scenario given/expect row cells, so that I can define inputs for complex objects and logic. > Note: Syntax highlighting and etc., are out of scope. Refer to: https://issues.jboss.org/browse/DROOLS-3514 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4574) Scenario test: UX to add an expression-based value.

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4574?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4574: -------------------------------------- Attachment: Screen Shot 2019-10-01 at 8.13.41 AM.png > Scenario test: UX to add an expression-based value. > ---------------------------------------------------- > > Key: DROOLS-4574 > URL: https://issues.jboss.org/browse/DROOLS-4574 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam > Attachments: Screen Shot 2019-10-01 at 8.13.41 AM.png > > > As a technical/advanced user (Cameron), I want to be able to input expression-based values in scenario given/expect row cells, so that I can define inputs for complex objects and logic. > Note: Syntax highlighting and etc., are out of scope. Refer to: https://issues.jboss.org/browse/DROOLS-3514 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4585) Focus doesn't moves after the selected cell

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4585?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-4585: ------------------------------------- Yes, but as we use the same grid framework for both, I think would be worth to fix both by one fix. What do you think [~karreiro]? > Focus doesn't moves after the selected cell > ------------------------------------------- > > Key: DROOLS-4585 > URL: https://issues.jboss.org/browse/DROOLS-4585 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.28.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Major > Labels: CustomerFocus > > {color:red}*Failure*{color} > If you navigate cell that is obscured by the right panel in header then it dosen't automatically scrolls to it as it done for grid body. > *Expected* > Viewed part of grid follows the selected cell -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-220) Operator is missing pod network settings

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFWIP-220?page=com.atlassian.jira.plugin.... ] Martin Choma updated WFWIP-220: ------------------------------- Summary: Operator is missing pod network settings (was: Operator is missing pod network setting) > Operator is missing pod network settings > ---------------------------------------- > > Key: WFWIP-220 > URL: https://issues.jboss.org/browse/WFWIP-220 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Choma > Assignee: Jeff Mesnil > Priority: Critical > > As a user I am able to tweak network configuration > {code:yaml} > dnsPolicy: > hostAliases: > hostIPC: > hostNetwork: > hostPID: > hostname: > subdomain: > {code} > [1] https://docs.openshift.com/container-platform/3.11/rest_api/apis-apps/v1b... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2019