July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10724) Deployed JSF application crashing with MyFaces 2.3.x due to unresolved dependency

by Erick de Oliveira Leal (JIRA)

Erick de Oliveira Leal created WFLY-10724: --------------------------------------------- Summary: Deployed JSF application crashing with MyFaces 2.3.x due to unresolved dependency Key: WFLY-10724 URL: https://issues.jboss.org/browse/WFLY-10724 Project: WildFly Issue Type: Bug Reporter: Erick de Oliveira Leal Assignee: Jason Greene Attachments: server.log java.lang.NoClassDefFoundError: org/apache/tomcat/InstanceManager -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10724) Deployed JSF application crashing with MyFaces 2.3.x due to unresolved dependency

by Erick de Oliveira Leal (JIRA)

[ https://issues.jboss.org/browse/WFLY-10724?page=com.atlassian.jira.plugin... ] Erick de Oliveira Leal updated WFLY-10724: ------------------------------------------ Description: Deployed JSF application will crash with installed MyFaces 2.3.1, see attached log. java.lang.NoClassDefFoundError: org/apache/tomcat/InstanceManager was:java.lang.NoClassDefFoundError: org/apache/tomcat/InstanceManager > Deployed JSF application crashing with MyFaces 2.3.x due to unresolved dependency > --------------------------------------------------------------------------------- > > Key: WFLY-10724 > URL: https://issues.jboss.org/browse/WFLY-10724 > Project: WildFly > Issue Type: Bug > Reporter: Erick de Oliveira Leal > Assignee: Jason Greene > Attachments: server.log > > > Deployed JSF application will crash with installed MyFaces 2.3.1, see attached log. > java.lang.NoClassDefFoundError: org/apache/tomcat/InstanceManager -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10567) Broken JSF module installer

by Erick de Oliveira Leal (JIRA)

[ https://issues.jboss.org/browse/WFLY-10567?page=com.atlassian.jira.plugin... ] Erick de Oliveira Leal commented on WFLY-10567: ----------------------------------------------- I tried last nightly wildfly-14.0.0.Beta2-SNAPSHOT and it still show this error. I can see it copies /javax(jsf-api) and /com(jsf-impl) folders under /modules but not org/apache(digester) and org/jboss(injection) _C:\Users\erick\AppData\Local\Temp\vfs\cli-1532189053608\cli-15321890536081d5203ba4c9a90ec\install-myfaces-2.3.1.cli-295c81d24a3ed039\C, if you defined a nonexistent resource on purpose you should use the --allow-nonexistent-resources option_ > Broken JSF module installer > --------------------------- > > Key: WFLY-10567 > URL: https://issues.jboss.org/browse/WFLY-10567 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 14.0.0.CR1 > Reporter: Jan Kašík > Assignee: Dmitrii Tikhomirov > Fix For: 14.0.0.CR1 > > Attachments: hello-jsf-version-0.0.1-SNAPSHOT.war > > > It is currently not possible to deploy *.cli built by multi-jsf-installer shipped with WildFly. When attempting to deploy, this message will appear: > {code} > org.jboss.as.cli.CommandFormatException: org.jboss.as.cli.CommandLineException: java.util.concurrent.ExecutionException: org.jboss.as.cli.CommandLineException: Failed to locate /tmp/vfs/cli-1528866094723/cli-1528866094723450313ef1dc90cff/install-mojarra-2.2.17.cli-212b6d42ba0c47e1/jsf-api-2.2.17.jar, if you defined a nonexistent resource on purpose you should use the --allow-nonexistent-resources option > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10723) Jboss AS 7.1 didn't read the deployment folders

by Veeresham Kardas (JIRA)

Veeresham Kardas created WFLY-10723: --------------------------------------- Summary: Jboss AS 7.1 didn't read the deployment folders Key: WFLY-10723 URL: https://issues.jboss.org/browse/WFLY-10723 Project: WildFly Issue Type: Bug Components: EE Affects Versions: JBoss AS7 7.1.1.Final Reporter: Veeresham Kardas Priority: Minor I have an EAR deployed on Jboss AS 7.1.1.Final running on Solaris. When I started the jboss, it didn't picked up the deployements and no error in the log (boot.log and server.log). The server.log on the day doesn't print that it looking for deployements and no log with {code:java} JBAS015874: JBoss AS 7.1.1.Final "Brontes" started {code} On a successful start day, the server.log is {code:java} 06:30:05,391 INFO [jacorb] JBAS016330: CORBA ORB Service started 06:30:05,475 INFO [scanner] JBAS015012: Started FileSystemDeploymentService for directory /home/veeresh/apps/jboss-as-7.1.1.Final/standalone/deployments 06:30:05,476 INFO [remoting] JBAS017100: Listening on localhost/127.0.0.1:20499 06:30:05,476 INFO [remoting] JBAS017100: Listening on tkjsbsvp1a/127.0.0.1:14947 .... .... 06:30:06,319 INFO [as] JBAS015951: Admin console listening on http://127.0.0.1:20490 06:30:06,320 INFO [as] JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 3600ms - Started 262 of 344 services (78 services are passive or on-demand) {code} After waiting for 15 mins, the process was killed and re-started and it worked fine without any changes and issues. This happened only once and not able to re-produce -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10722) Update MyFaces to 2.3.1, EE 8 compliant

by Erick de Oliveira Leal (JIRA)

[ https://issues.jboss.org/browse/WFLY-10722?page=com.atlassian.jira.plugin... ] Erick de Oliveira Leal updated WFLY-10722: ------------------------------------------ Summary: Update MyFaces to 2.3.1, EE 8 compliant (was: Sync MyFaces to 2.3.1, part of Java 88) > Update MyFaces to 2.3.1, EE 8 compliant > --------------------------------------- > > Key: WFLY-10722 > URL: https://issues.jboss.org/browse/WFLY-10722 > Project: WildFly > Issue Type: Component Upgrade > Components: JSF > Affects Versions: 13.0.0.Final > Reporter: Erick de Oliveira Leal > Assignee: Farah Juma > > Currently, MyFaces defaults to 2.2.11, it makes sense update it to 2.3.1. Since it is compliant to EE 8. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10722) Sync MyFaces to 2.3.1, part of Java 88

by Erick de Oliveira Leal (JIRA)

Erick de Oliveira Leal created WFLY-10722: --------------------------------------------- Summary: Sync MyFaces to 2.3.1, part of Java 88 Key: WFLY-10722 URL: https://issues.jboss.org/browse/WFLY-10722 Project: WildFly Issue Type: Component Upgrade Components: JSF Affects Versions: 13.0.0.Final Reporter: Erick de Oliveira Leal Assignee: Farah Juma Currently, MyFaces defaults to 2.2.11, it makes sense update it to 2.3.1. Since it is compliant to EE 8. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

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

by Michael Anstis (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2755?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-2755: ----------------------------------- Sprint: 2018 Week 30-32 (was: 2018 Week 27-29) > [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 > Components: DMN Editor > 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)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2707) CSS for test results panel/dock design

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2707?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2707: ------------------------------------- Looks great, thanks [~srambach]! > CSS for test results panel/dock design > -------------------------------------- > > Key: DROOLS-2707 > URL: https://issues.jboss.org/browse/DROOLS-2707 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Sarah Rambacher > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screen Shot 2018-07-05 at 11.33.41 AM.png, Screen Shot 2018-07-11 at 3.03.50 PM.png > > > As a business analyst I want the ability to review simulation test results so that I can view the accuracy of my rules. > *Verification conditions:* > - CSS styles that employ relevant PatternFly styles and/or patterns, such as: http://www.patternfly.org/pattern-library/data-visualization/donut-chart/... > - CSS that articulates the design wireframe attached, and: > https://redhat.invisionapp.com/share/BVKORFBUJ24#/screens/302476070 > https://docs.google.com/document/d/1I_ghU9An--uQRzuVV9zXB387HLYjZcc01LXFX... > - Reviewed by scrum team prior to PR/dev delivery. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2707) CSS for test results panel/dock design

by Sarah Rambacher (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2707?page=com.atlassian.jira.plugi... ] Sarah Rambacher commented on DROOLS-2707: ----------------------------------------- Updated to add space between dl items. https://cdn.rawgit.com/srambach/BxMS-frontend/fdf3d076f925b3c73d288ccf116... Pull request: https://github.com/srambach/BxMS-frontend/pull/71 Branch: https://github.com/srambach/BxMS-frontend/tree/drools-2707-results-panel [~uxdlc] [~danielezonca] > CSS for test results panel/dock design > -------------------------------------- > > Key: DROOLS-2707 > URL: https://issues.jboss.org/browse/DROOLS-2707 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Liz Clayton > Assignee: Sarah Rambacher > Labels: ScenarioSimulation, UX, UXTeam > Attachments: Screen Shot 2018-07-05 at 11.33.41 AM.png, Screen Shot 2018-07-11 at 3.03.50 PM.png > > > As a business analyst I want the ability to review simulation test results so that I can view the accuracy of my rules. > *Verification conditions:* > - CSS styles that employ relevant PatternFly styles and/or patterns, such as: http://www.patternfly.org/pattern-library/data-visualization/donut-chart/... > - CSS that articulates the design wireframe attached, and: > https://redhat.invisionapp.com/share/BVKORFBUJ24#/screens/302476070 > https://docs.google.com/document/d/1I_ghU9An--uQRzuVV9zXB387HLYjZcc01LXFX... > - Reviewed by scrum team prior to PR/dev delivery. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3970) Reload Elytron ldap-key-store using JBoss CLI

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3970?page=com.atlassian.jira.plugi... ] Farah Juma moved EAP7-1064 to WFCORE-3970: ------------------------------------------ Project: WildFly Core (was: EAP 7 Planning Pilot) Key: WFCORE-3970 (was: EAP7-1064) Issue Type: Feature Request (was: Requirement) Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0) Component/s: Security (was: Security) 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) > Reload Elytron ldap-key-store using JBoss CLI > --------------------------------------------- > > Key: WFCORE-3970 > URL: https://issues.jboss.org/browse/WFCORE-3970 > Project: WildFly Core > Issue Type: Feature Request > Components: Security > Reporter: Farah Juma > Assignee: Justin Cook > > It is not possible to reload the certificates dynamically for Elytron's *ldap-key-store*. > If some changes have been made in the certificates present in LDAP directory then EAP needs to be restarted first in order to see those changes done in LDAP directory which is not ideal for production environments. > For simple file based keystores, *load* operation is available : > ------------------------- > [standalone@localhost:9990 /] /subsystem=elytron/key-store=twoWayKS:load() > ------------------------- > But this option is missing for *ldap-key-store* : > ------------------------- > [standalone@localhost:9990 /] /subsystem=elytron/ldap-key-store=LKS1:load() > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0031: No operation named 'load' exists at address [ > (\"subsystem\" => \"elytron\"), > (\"ldap-key-store\" => \"LKS1\") > ]", > "rolled-back" => true > } > ------------------------- > There should be such option available to reload the content of ldap-key-store without restarting the EAP server. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 12 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 July 2018