January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10315) Restore legacy (not "graceful") startup mode

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-10315?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-10315: --------------------------------------- Assignee: (was: Jason Greene) > Restore legacy (not "graceful") startup mode > -------------------------------------------- > > Key: WFLY-10315 > URL: https://issues.jboss.org/browse/WFLY-10315 > Project: WildFly > Issue Type: Feature Request > Components: Management > Reporter: Vladimir Grabarchuk > Priority: Major > > Please allow a configurable legacy startup mode which was the default before WF11, when components can service HTTP requests as soon as they are deployed, not when the container deploys all components. > The use case for this is the following: there is a configuration service component upon which other components depend for configuration data, requested and served via a HTTP request. With the new "graceful startup" this scenario no longer seems possible, as it results in read timeouts, mis-configured artifacts, and failed deployments altogether. > If generally feasible, another value of the *--start-mode=legacy* seems appropriate to accommodate the original (legacy) behavior. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4291) Restore legacy (not "graceful") startup mode

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4291?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-10315 to WFCORE-4291: ------------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-4291 (was: WFLY-10315) Component/s: Management (was: Management) > Restore legacy (not "graceful") startup mode > -------------------------------------------- > > Key: WFCORE-4291 > URL: https://issues.jboss.org/browse/WFCORE-4291 > Project: WildFly Core > Issue Type: Feature Request > Components: Management > Reporter: Vladimir Grabarchuk > Priority: Major > > Please allow a configurable legacy startup mode which was the default before WF11, when components can service HTTP requests as soon as they are deployed, not when the container deploys all components. > The use case for this is the following: there is a configuration service component upon which other components depend for configuration data, requested and served via a HTTP request. With the new "graceful startup" this scenario no longer seems possible, as it results in read timeouts, mis-configured artifacts, and failed deployments altogether. > If generally feasible, another value of the *--start-mode=legacy* seems appropriate to accommodate the original (legacy) behavior. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10564) Replace "Invalid driver name" with something helpful

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-10564?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-10564: ------------------------------------ Component/s: JCA > Replace "Invalid driver name" with something helpful > ---------------------------------------------------- > > Key: WFLY-10564 > URL: https://issues.jboss.org/browse/WFLY-10564 > Project: WildFly > Issue Type: Enhancement > Components: JCA > Affects Versions: 13.0.0.Final > Reporter: Karl-Philipp Richter > Assignee: Jason Greene > Priority: Major > > Entering `postgresql` in the "Driver name" text field during creation of a data source in the data source configuration section causes the validation constraint violation label "Invalid driver name" to be displayed. Validation constraint violation messages which don't contain explain the constraints or better the reason for the failure are not helpful as any other error message not explaining the reason for the failure. > Since the occurrence of such a bad error message show severe lack of quality assurance, I suggest to review the software development process and refrain from any releases until counter-mechanisms (code reviews by programmers or UX specialists sensitized/educated to spot such issues, hallway-tests, etc.). Your software quality with rocket through the ceiling. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10564) Replace "Invalid driver name" with something helpful

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-10564?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-10564: --------------------------------------- Assignee: Stefano Maestri (was: Jason Greene) > Replace "Invalid driver name" with something helpful > ---------------------------------------------------- > > Key: WFLY-10564 > URL: https://issues.jboss.org/browse/WFLY-10564 > Project: WildFly > Issue Type: Enhancement > Components: JCA > Affects Versions: 13.0.0.Final > Reporter: Karl-Philipp Richter > Assignee: Stefano Maestri > Priority: Major > > Entering `postgresql` in the "Driver name" text field during creation of a data source in the data source configuration section causes the validation constraint violation label "Invalid driver name" to be displayed. Validation constraint violation messages which don't contain explain the constraints or better the reason for the failure are not helpful as any other error message not explaining the reason for the failure. > Since the occurrence of such a bad error message show severe lack of quality assurance, I suggest to review the software development process and refrain from any releases until counter-mechanisms (code reviews by programmers or UX specialists sensitized/educated to spot such issues, hallway-tests, etc.). Your software quality with rocket through the ceiling. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10628) Define name in wildfly-jsf-injection's faces-config.xml

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-10628?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-10628: --------------------------------------- Assignee: Farah Juma (was: Jason Greene) > Define name in wildfly-jsf-injection's faces-config.xml > ------------------------------------------------------- > > Key: WFLY-10628 > URL: https://issues.jboss.org/browse/WFLY-10628 > Project: WildFly > Issue Type: Enhancement > Components: JSF > Affects Versions: 10.1.0.Final > Reporter: Vsevolod Golovanov > Assignee: Farah Juma > Priority: Major > > A name allows configuring specific load order in application's faces-config.xml. Does it matter for such a small and seemingly order agnostic lib as wildlfy-jsf-injection? It would've simplified working around WELD-2512... And it's a trivial change. Something like: > {code} > <?xml version="1.0" encoding="utf-8"?> > <faces-config 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/web-facesconfig_2_2.xsd" > version="2.2"> > <name>wildfly_jsf_injection</name> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10648) curly brackets {} not working in url

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-10648?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-10648: ------------------------------------ Component/s: Web (Undertow) > curly brackets {} not working in url > ------------------------------------ > > Key: WFLY-10648 > URL: https://issues.jboss.org/browse/WFLY-10648 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 13.0.0.Final > Reporter: Arun Kumar > Assignee: Jason Greene > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10648) curly brackets {} not working in url

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-10648?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-10648: --------------------------------------- Assignee: Flavia Rainone (was: Jason Greene) > curly brackets {} not working in url > ------------------------------------ > > Key: WFLY-10648 > URL: https://issues.jboss.org/browse/WFLY-10648 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 13.0.0.Final > Reporter: Arun Kumar > Assignee: Flavia Rainone > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10628) Define name in wildfly-jsf-injection's faces-config.xml

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-10628?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-10628: ------------------------------------ Component/s: JSF > Define name in wildfly-jsf-injection's faces-config.xml > ------------------------------------------------------- > > Key: WFLY-10628 > URL: https://issues.jboss.org/browse/WFLY-10628 > Project: WildFly > Issue Type: Enhancement > Components: JSF > Affects Versions: 10.1.0.Final > Reporter: Vsevolod Golovanov > Assignee: Jason Greene > Priority: Major > > A name allows configuring specific load order in application's faces-config.xml. Does it matter for such a small and seemingly order agnostic lib as wildlfy-jsf-injection? It would've simplified working around WELD-2512... And it's a trivial change. Something like: > {code} > <?xml version="1.0" encoding="utf-8"?> > <faces-config 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/web-facesconfig_2_2.xsd" > version="2.2"> > <name>wildfly_jsf_injection</name> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

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

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-10710?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-10710: --------------------------------------- Assignee: (was: Jason Greene) > 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 > Priority: Major > Attachments: Keycloak -OKTA-Config.docx, WildflyKeycloakOktaSequence.png > > > 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.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10732) Deployment Issue with wldfly

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-10732?page=com.atlassian.jira.plugin... ] Brian Stansberry resolved WFLY-10732. ------------------------------------- Assignee: (was: Jason Greene) Resolution: Rejected Please use the forums to request community assistance. > Deployment Issue with wldfly > ---------------------------- > > Key: WFLY-10732 > URL: https://issues.jboss.org/browse/WFLY-10732 > Project: WildFly > Issue Type: Feature Request > Reporter: HarithaReddy Padala > Priority: Major > > Team, > We have our application based on EJB nd struts1.x.It is not getting properly deployed on JBOSS wild fly 1.1. We are trying in stand alone mode. > For our appl to be up and running we have dependency with 3ears and two wars. We added those in the jboss deployment structure. > Still it is not able to recognize. Can you suggest what needs to be done -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 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 January 2019