May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2611) Unify JSF action listener and CDI integration

by Erick de Oliveira Leal (JIRA)

[ https://issues.jboss.org/browse/WFLY-2611?page=com.atlassian.jira.plugin.... ] Erick de Oliveira Leal commented on WFLY-2611: ---------------------------------------------- https://github.com/javaserverfaces/mojarra/issues/3482 > Unify JSF action listener and CDI integration > --------------------------------------------- > > Key: WFLY-2611 > URL: https://issues.jboss.org/browse/WFLY-2611 > Project: WildFly > Issue Type: Feature Request > Components: CDI / Weld, JSF > Affects Versions: 8.0.0.CR1 > Reporter: Tomas Remes > Assignee: Farah Juma > > There are three ways, how can user specify custom JSF action listener: > 1. Method binding - with actionListener param. This case is ok, meaning CDI injection and interceptor works for given method/bean. > 2. Providing custom implementation - <f:actionListener type="org.jboss.jsf.listeners.MyActionListener"/>. In this case CDI doesn't work at all for processAction method of given class. > 3. Defining in faces-config - in this case CDI injection works, but interceptor is not executed. > Reproducer available at https://github.com/tremes/javaee7-samples/tree/cdi-testing/jsf/actionlist.... Test can be executed with "mvn clean test -Pwildfly-managed-arquillian" or "mvn clean test -Pwildfly-remote-arquillian" and IMHO all should pass. > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1184) FAMILY and HASH selectors in Elytron client are parsed incorrectly

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/ELY-1184?page=com.atlassian.jira.plugin.s... ] Chao Wang reassigned ELY-1184: ------------------------------ Assignee: Chao Wang (was: Darran Lofthouse) > FAMILY and HASH selectors in Elytron client are parsed incorrectly > ------------------------------------------------------------------ > > Key: ELY-1184 > URL: https://issues.jboss.org/browse/ELY-1184 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta42 > Reporter: Ondrej Lukas > Assignee: Chao Wang > Priority: Critical > > When #FAMILY or #HASH selector is used in Elytron client configuration file then it is parsed incorrectly - end bracket ')' is included in parsed family/hash name - it means it results to {{DIGEST)}} instead of {{DIGEST}}. It seems it is parsed incorrectly in {{parseSpecialWithName}} method of {{org.wildfly.security.sasl.SaslMechanismSelector}} class in [1]. > Following element for selector is used in Elytron client configuration file: > {code} > ... > <sasl-mechanism-selector selector="#FAMILY(DIGEST)"/> > ... > {code} > [1] https://github.com/wildfly-security/wildfly-elytron/blob/master/src/main/... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AG-24) Fix username property in the connection factory

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-24?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro resolved AG-24. ----------------------------- Resolution: Done > Fix username property in the connection factory > ----------------------------------------------- > > Key: AG-24 > URL: https://issues.jboss.org/browse/AG-24 > Project: Agroal > Issue Type: Bug > Components: pool > Affects Versions: 0.1 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Priority: Minor > Fix For: 0.2 > > > JDBC drivers use 'user' as the default property name -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AG-24) Fix username property in the connection factory

by Luis Barreiro (JIRA)

Luis Barreiro created AG-24: ------------------------------- Summary: Fix username property in the connection factory Key: AG-24 URL: https://issues.jboss.org/browse/AG-24 Project: Agroal Issue Type: Bug Components: pool Affects Versions: 0.1 Reporter: Luis Barreiro Assignee: Luis Barreiro Priority: Minor Fix For: 0.2 JDBC drivers use 'user' as the default property name -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8820) Upgrade EJB client to 4.0.0.Beta29

by David Lloyd (JIRA)

David Lloyd created WFLY-8820: --------------------------------- Summary: Upgrade EJB client to 4.0.0.Beta29 Key: WFLY-8820 URL: https://issues.jboss.org/browse/WFLY-8820 Project: WildFly Issue Type: Component Upgrade Reporter: David Lloyd Assignee: Jason Greene -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8820) Upgrade EJB client to 4.0.0.Beta29

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-8820?page=com.atlassian.jira.plugin.... ] David Lloyd reassigned WFLY-8820: --------------------------------- Assignee: David Lloyd (was: Jason Greene) > Upgrade EJB client to 4.0.0.Beta29 > ---------------------------------- > > Key: WFLY-8820 > URL: https://issues.jboss.org/browse/WFLY-8820 > Project: WildFly > Issue Type: Component Upgrade > Reporter: David Lloyd > Assignee: David Lloyd > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2860) The ReloadRedirectTestCase needs to work with Elytron

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2860?page=com.atlassian.jira.plugi... ] James Perkins reassigned WFCORE-2860: ------------------------------------- Assignee: Jean-Francois Denise (was: Tomaz Cerar) > The ReloadRedirectTestCase needs to work with Elytron > ----------------------------------------------------- > > Key: WFCORE-2860 > URL: https://issues.jboss.org/browse/WFCORE-2860 > Project: WildFly Core > Issue Type: Task > Components: CLI, Test Suite > Reporter: James Perkins > Assignee: Jean-Francois Denise > > The {{ReloadRedirectTestCase}} test configures an SSL management connection. This doesn't work when Elytron is enabled ({{-Delytron}} for the test suite) because the {{/core-service=management/security-realm=ManagementRealm/}} is not used. An SSL context will need to be created on the Elytron subsystem and the management interface will need to use that context. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2860) The ReloadRedirectTestCase needs to work with Elytron

by James Perkins (JIRA)

James Perkins created WFCORE-2860: ------------------------------------- Summary: The ReloadRedirectTestCase needs to work with Elytron Key: WFCORE-2860 URL: https://issues.jboss.org/browse/WFCORE-2860 Project: WildFly Core Issue Type: Task Components: CLI, Test Suite Reporter: James Perkins Assignee: Tomaz Cerar The {{ReloadRedirectTestCase}} test configures an SSL management connection. This doesn't work when Elytron is enabled ({{-Delytron}} for the test suite) because the {{/core-service=management/security-realm=ManagementRealm/}} is not used. An SSL context will need to be created on the Elytron subsystem and the management interface will need to use that context. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8762) WebSocketsDefinition BUFFER_POOL and WORKER are not configured as capability references

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8762?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-8762: ----------------------------------- Found the problem, it is related to completely broken RestartParent* handlers after the fix this is result: {noformat} [standalone@localhost:9990 /] /subsystem=io/worker=default:remove { "outcome" => "failed", "failure-description" => "WFLYCTL0367: Cannot remove capability 'org.wildfly.io.worker.default' as it is required by other capabilities: capability 'org.wildfly.undertow.listener.default' requires it for attribute 'worker' at address '/subsystem=undertow/server=default-server/http-listener=default' capability 'org.wildfly.remoting.endpoint' requires it for attribute 'worker' at address '/subsystem=remoting/configuration=endpoint' capability 'org.wildfly.undertow.listener.https' requires it for attribute 'worker' at address '/subsystem=undertow/server=default-server/https-listener=https' capability 'org.wildfly.undertow.servlet-container.websocket.default' requires it for attribute 'worker' at address '/subsystem=undertow/servlet-container=default/setting=websockets'", "rolled-back" => true } {noformat} > WebSocketsDefinition BUFFER_POOL and WORKER are not configured as capability references > --------------------------------------------------------------------------------------- > > Key: WFLY-8762 > URL: https://issues.jboss.org/browse/WFLY-8762 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Brian Stansberry > Assignee: Tomaz Cerar > > This makes it hard to remove or rename the 'default' worker (e.g. as part of doing performance tuning), because the requirement for that worker isn't shown in standalone.xml. Since there's no capability ref failure, boot proceeds to RUNTIME, ServletContainerService can't start but a whole lot of others can't start as well. So there's a lot of noise that obscures the issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2754) Propagate sasl-mechanism-selector to elytron subsystem

by Stefan Guilhen (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2754?page=com.atlassian.jira.plugi... ] Stefan Guilhen reassigned WFCORE-2754: -------------------------------------- Assignee: Stefan Guilhen > Propagate sasl-mechanism-selector to elytron subsystem > ------------------------------------------------------ > > Key: WFCORE-2754 > URL: https://issues.jboss.org/browse/WFCORE-2754 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta16 > Reporter: Martin Švehla > Assignee: Stefan Guilhen > Priority: Blocker > > sasl-mechanism-selector was introduced to Elytron client configuration to allow whitelisting specific SASL mechanism in the client. See WFCORE-2615 for the discussion. > This element should be also propagated to Elytron subsystem so it's available server side. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 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 May 2017