February 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFLY-14442) $JBOSS_HOME/docs/schema/jboss-app_* contain wrong links inside the documentation elements

by Parul Sharma (Jira)

[ https://issues.redhat.com/browse/WFLY-14442?page=com.atlassian.jira.plugi... ] Parul Sharma moved JBEAP-21028 to WFLY-14442: --------------------------------------------- Component/s: Server (was: Server) (was: User Experience) Key: WFLY-14442 (was: JBEAP-21028) Affects Version/s: (was: 7.4.0.Beta) (was: 7.3.5.GA) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Project: WildFly (was: JBoss Enterprise Application Platform) > $JBOSS_HOME/docs/schema/jboss-app_* contain wrong links inside the documentation elements > ----------------------------------------------------------------------------------------- > > Key: WFLY-14442 > URL: https://issues.redhat.com/browse/WFLY-14442 > Project: WildFly > Issue Type: Bug > Components: Server > Reporter: Parul Sharma > Assignee: Parul Sharma > Priority: Major > > jboss-app_8_0.xsd > jboss-app_7_0.xsd > jboss-app_7_1.xsd > files suggest users to use links > https://www.jboss.org/j2ee/schema/jboss-app_7_0.xsd > http://www.jboss.org/j2ee/schema/jboss-app_7_1.xsd > http://www.jboss.org/j2ee/schema/jboss-app_8_0.xsd > which are not working any more. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFLY-13306) Deployment of empty war with 2.3 faces-config.xml fails

by Parul Sharma (Jira)

[ https://issues.redhat.com/browse/WFLY-13306?page=com.atlassian.jira.plugi... ] Parul Sharma commented on WFLY-13306: ------------------------------------- Hi [~wolfgangknauf], if you are using JSF version 2.3 then it will give you the error because JSF 2.3 needs CDI but CDI is not set up and no beans.xml is present. If you want to overcome this issue we have the following ways: 1. Use JSF 2.2 instead of 2.3. 2. Add a beans.xml to the WEB_INF directory <beans xmlns="[http://xmlns.jcp.org/xml/ns/javaee]" xmlns:xsi="[http://www.w3.org/2001/XMLSchema-instance]" xsi:schemaLocation=" [http://xmlns.jcp.org/xml/ns/javaee] [http://xmlns.jcp.org/xml/ns/javaee/beans_1_1.xsd]" bean-discovery-mode="annotated"> </beans> 3. Just create a @NAMED bean. Thanks > Deployment of empty war with 2.3 faces-config.xml fails > ------------------------------------------------------- > > Key: WFLY-13306 > URL: https://issues.redhat.com/browse/WFLY-13306 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 19.0.0.Final, 21.0.0.Beta1 > Reporter: Wolfgang Knauf > Assignee: Parul Sharma > Priority: Major > Attachments: JsfSample.zip > > > Attached sample is created from the archetype "wildfly-jakartaee-webapp-archetype" found at [https://github.com/wildfly/wildfly-archetypes/] (still 18.0, an update for WildFly 19.0 is currently in work). It is an empty project, the only change is that in "faces-config.xml" the version was changed from 2.2 to 2.3. > Deployment fails with this exception: > {quote} > 2020-03-30 20:05:45,200 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 83) Critical error during deployment: : com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null > at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:357) > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:205) > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187) > at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:217) > at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:186) > 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:1541) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1541) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1541) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1541) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1541) > 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) > at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) > at java.util.concurrent.FutureTask.run(Unknown Source) > 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(Unknown Source) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > Caused by: java.lang.NullPointerException > at com.sun.faces.facelets.impl.DefaultResourceResolver.resolveUrl(DefaultResourceResolver.java:40) > at com.sun.faces.facelets.impl.DefaultFaceletFactory.init(DefaultFaceletFactory.java:129) > at com.sun.faces.application.ApplicationAssociate.createFaceletFactory(ApplicationAssociate.java:849) > at com.sun.faces.application.ApplicationAssociate.initializeFacelets(ApplicationAssociate.java:342) > at com.sun.faces.application.ApplicationAssociate.getCompiler(ApplicationAssociate.java:420) > at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.process(FaceletTaglibConfigProcessor.java:217) > at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:341) > ... 23 more > 2020-03-30 20:05:45,207 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 83) MSC000001: Failed to start service jboss.deployment.unit."JsfSample.war".undertow-deployment: org.jboss.msc.service.StartException in service jboss.deployment.unit."JsfSample.war".undertow-deployment: java.lang.RuntimeException: java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:81) > at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) > at java.util.concurrent.FutureTask.run(Unknown Source) > 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(Unknown Source) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > Caused by: java.lang.RuntimeException: java.lang.RuntimeException: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:254) > 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.RuntimeException: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:283) > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187) > at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:217) > at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:186) > 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:1541) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1541) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1541) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1541) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1541) > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:252) > ... 10 more > Caused by: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null > at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:357) > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:205) > ... 22 more > Caused by: java.lang.NullPointerException > at com.sun.faces.facelets.impl.DefaultResourceResolver.resolveUrl(DefaultResourceResolver.java:40) > at com.sun.faces.facelets.impl.DefaultFaceletFactory.init(DefaultFaceletFactory.java:129) > at com.sun.faces.application.ApplicationAssociate.createFaceletFactory(ApplicationAssociate.java:849) > at com.sun.faces.application.ApplicationAssociate.initializeFacelets(ApplicationAssociate.java:342) > at com.sun.faces.application.ApplicationAssociate.getCompiler(ApplicationAssociate.java:420) > at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.process(FaceletTaglibConfigProcessor.java:217) > at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:341) > ... 23 more > {quote} > When adding an empty "beans.xml" file or any CDI annotated class, the error disappears. > It also works when declaring JSF version 2.2. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFLY-14441) Currency ProtoStream marshaller needs to tolerate locales with no default currency

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-14441: ----------------------------------- Summary: Currency ProtoStream marshaller needs to tolerate locales with no default currency Key: WFLY-14441 URL: https://issues.redhat.com/browse/WFLY-14441 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: No Release Reporter: Paul Ferraro Assignee: Paul Ferraro or where default currency cannot be determined. See: https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/util/Cu... -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFLY-14441) Currency ProtoStream marshaller needs to tolerate locales with no default currency

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-14441?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-14441: -------------------------------- Workaround: Workaround Exists > Currency ProtoStream marshaller needs to tolerate locales with no default currency > ---------------------------------------------------------------------------------- > > Key: WFLY-14441 > URL: https://issues.redhat.com/browse/WFLY-14441 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: No Release > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > > or where default currency cannot be determined. > See: https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/util/Cu... -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5172) [DMN Designer] Graph - Default names for input nodes

by Amy Glass (Jira)

[ https://issues.redhat.com/browse/DROOLS-5172?page=com.atlassian.jira.plug... ] Amy Glass reassigned DROOLS-5172: --------------------------------- Assignee: Mario Fusco (was: Elizabeth Clayton) > [DMN Designer] Graph - Default names for input nodes > ---------------------------------------------------- > > Key: DROOLS-5172 > URL: https://issues.redhat.com/browse/DROOLS-5172 > Project: Drools > Issue Type: Task > Reporter: Guilherme Gomes > Assignee: Mario Fusco > Priority: Major > Labels: drools-tools > > When users update the type of a recently created input node, they usually change the node name from “InputData–1” to “Person” (if the new type is “Person”). > Should we do this automatically? Should we ask for the type when users create an input node? Should we apply the same approach for other nodes (BKMs, Decisions, etc.)? > This UX JIRA aims to cover these open questions, to enhance the user experience when they are creating new nodes in the canvas. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5651) [DMN Designer] Multiple DRDs interactions review

by Amy Glass (Jira)

[ https://issues.redhat.com/browse/DROOLS-5651?page=com.atlassian.jira.plug... ] Amy Glass reassigned DROOLS-5651: --------------------------------- Assignee: Guilherme Gomes (was: Elizabeth Clayton) > [DMN Designer] Multiple DRDs interactions review > ------------------------------------------------ > > Key: DROOLS-5651 > URL: https://issues.redhat.com/browse/DROOLS-5651 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: UXTeam > > The current multiple DRDs support in the editor follows the guided lines provided on this UX team guidelines: > - on this document: https://docs.google.com/document/d/14pnw6QUTj5BsUJyz4uP_ozLLkYBvCYGXd1VIa... > - and, on this mockup: https://marvelapp.com/prototype/jb9i419/screen/62691972 and > However, during the development, and the PR review, some corner case scenarios emerged. > This JIRA comprehends UX output for those points. Some feedbacks provided by Jan will be quite helpful to guide this investigation:: > - User can't create DRD before an element is added to the diagram (source: https://github.com/kiegroup/kie-wb-common/pull/3379#issuecomment-689614893) > - The icon for DRD-related actions is the sign used commonly for "Share" (source comment: https://github.com/kiegroup/kie-wb-common/pull/3379#issuecomment-689614893) > - There's no clear indication of what DRD or DRG I am currently seeing (other than checking the decision components present on canvas) > - It would be nice if the currently selected node on canvas would be highlighted in the Decision Navigator too. > Besides these scenarios raised by Jan. I'm starting thinking about behaviors like this: > - I have a DRG with 3 nodes: Input, Decision, BKM > - I create DRD with my Input and my Decision > - If I come back to the DRG and delete the Input, we're also deleting it from the DRD, because the DRG represents the global context. Should we really delete nodes from the subset? -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5651) [DMN Designer] Multiple DRDs interactions review

by Amy Glass (Jira)

[ https://issues.redhat.com/browse/DROOLS-5651?page=com.atlassian.jira.plug... ] Amy Glass commented on DROOLS-5651: ----------------------------------- Removing UX assignee until prioritized. > [DMN Designer] Multiple DRDs interactions review > ------------------------------------------------ > > Key: DROOLS-5651 > URL: https://issues.redhat.com/browse/DROOLS-5651 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: UXTeam > > The current multiple DRDs support in the editor follows the guided lines provided on this UX team guidelines: > - on this document: https://docs.google.com/document/d/14pnw6QUTj5BsUJyz4uP_ozLLkYBvCYGXd1VIa... > - and, on this mockup: https://marvelapp.com/prototype/jb9i419/screen/62691972 and > However, during the development, and the PR review, some corner case scenarios emerged. > This JIRA comprehends UX output for those points. Some feedbacks provided by Jan will be quite helpful to guide this investigation:: > - User can't create DRD before an element is added to the diagram (source: https://github.com/kiegroup/kie-wb-common/pull/3379#issuecomment-689614893) > - The icon for DRD-related actions is the sign used commonly for "Share" (source comment: https://github.com/kiegroup/kie-wb-common/pull/3379#issuecomment-689614893) > - There's no clear indication of what DRD or DRG I am currently seeing (other than checking the decision components present on canvas) > - It would be nice if the currently selected node on canvas would be highlighted in the Decision Navigator too. > Besides these scenarios raised by Jan. I'm starting thinking about behaviors like this: > - I have a DRG with 3 nodes: Input, Decision, BKM > - I create DRD with my Input and my Decision > - If I come back to the DRG and delete the Input, we're also deleting it from the DRD, because the DRG represents the global context. Should we really delete nodes from the subset? -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5172) [DMN Designer] Graph - Default names for input nodes

by Amy Glass (Jira)

[ https://issues.redhat.com/browse/DROOLS-5172?page=com.atlassian.jira.plug... ] Amy Glass commented on DROOLS-5172: ----------------------------------- Removing UX assignee until prioritized. > [DMN Designer] Graph - Default names for input nodes > ---------------------------------------------------- > > Key: DROOLS-5172 > URL: https://issues.redhat.com/browse/DROOLS-5172 > Project: Drools > Issue Type: Task > Reporter: Guilherme Gomes > Assignee: Mario Fusco > Priority: Major > Labels: drools-tools > > When users update the type of a recently created input node, they usually change the node name from “InputData–1” to “Person” (if the new type is “Person”). > Should we do this automatically? Should we ask for the type when users create an input node? Should we apply the same approach for other nodes (BKMs, Decisions, etc.)? > This UX JIRA aims to cover these open questions, to enhance the user experience when they are creating new nodes in the canvas. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-3330) DMN Properties panel - UX enhancements

by Amy Glass (Jira)

[ https://issues.redhat.com/browse/DROOLS-3330?page=com.atlassian.jira.plug... ] Amy Glass commented on DROOLS-3330: ----------------------------------- Removing UX assignee until prioritized. > DMN Properties panel - UX enhancements > --------------------------------------- > > Key: DROOLS-3330 > URL: https://issues.redhat.com/browse/DROOLS-3330 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Guilherme Gomes > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: ChlamydiaScreening_CQM.jpg, styles.png > > > # Increase the size of the Description input to a text field. > # Combine the three current style related menus (Background details, Font settings, Dimensions) into a single menu. > Notes re: Styles section: > * As the context of these items is very different from the other properties, it might be beneficial to the user to group them together thereby distinguishing them from the rest. > * The extra menu headers required for these additional menus takes up valuable screen real estate, that could otherwise be used by higher priority properties. > * If the user does want to use the style settings, we're creating additional work to make them both scroll down and open the additional related menus. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-4387) DMN editor: 7.6 Search - UX discovery/research

by Amy Glass (Jira)

[ https://issues.redhat.com/browse/DROOLS-4387?page=com.atlassian.jira.plug... ] Amy Glass reassigned DROOLS-4387: --------------------------------- Assignee: Guilherme Gomes (was: Elizabeth Clayton) > DMN editor: 7.6 Search - UX discovery/research > ---------------------------------------------- > > Key: DROOLS-4387 > URL: https://issues.redhat.com/browse/DROOLS-4387 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Guilherme Gomes > Priority: Major > Labels: UX, UXTeam, drools-tools > > Follow-up to https://issues.jboss.org/browse/DROOLS-4142, to extend the Find feature to search across the entire DMN file/tabs within the editor. > This story is to gather use cases, requirements and acceptance criteria as defined at: https://www.yodiz.com/blog/user-stories-acceptance-definition-and-criteri... > Verification conditions: Documented use case and acceptance criteria for this feature, particularly as it relates to user experience and design. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 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 February 2021