July 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9131) Wildfly 10.1.0 Fails to load JSF message bundle from Java class

by Bobby Bassman (JIRA)

[ https://issues.jboss.org/browse/WFLY-9131?page=com.atlassian.jira.plugin.... ] Bobby Bassman updated WFLY-9131: -------------------------------- Attachment: WFLY9131_01.png WFLY9131_02.png > Wildfly 10.1.0 Fails to load JSF message bundle from Java class > --------------------------------------------------------------- > > Key: WFLY-9131 > URL: https://issues.jboss.org/browse/WFLY-9131 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 10.1.0.Final > Environment: Windows 10 > Wildfly 10.1.0 > Reporter: Bobby Bassman > Assignee: Farah Juma > Attachments: WFLY9131_01.png, WFLY9131_02.png > > > Have a war application which deploys and runs correctly on EAP 6.4. When deploying on WIldfly 10.1.0, none of the message bundle lookups work, resulting in ???zxcv??? text on JSF pages. > This application has the following in faces-config.xml: > <application> > <locale-config> > <default-locale>en</default-locale> > <supported-locale>en_US</supported-locale> > <supported-locale>en</supported-locale> > </locale-config> > <message-bundle>com.rfdinc.efile.bp.resources.CombinedMessageResources</message-bundle> > <resource-bundle> > <base-name>com.rfdinc.efile.bp.resources.CombinedMessageResources</base-name> > <var>msg</var> > </resource-bundle> > </application> > Here, com.rfdinc.efile.bp.resources.CombinedMessageResources is a Java class which extends java.util.ResourceBundle and implements most of the methods of java.util.ResourceBundle. > This technique works correctly under EAP 6.4. Under Wildfly 10.1.0, however, none of the class methods ever get called. This was verified by placing logger messages throughout com.rfdinc.efile.bp.resources.CombinedMessageResources. > Replacing <message-bundle> and <base-name> with a 'properties' file works, but this particular Java class allows us to combine multiple property files into a single resource bundle. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9146) Legacy protocol write-attribute operations throw NoSuchResourceException

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-9146?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-9146: ------------------------------- Description: In this operation sequence, the 2nd operation fails with a NoSuchResourceException: /subsystem=jgroups/stack=tcp/protocol=TCPPING:add() /subsystem=jgroups/stack=tcp/protocol=TCPPING:write-attribute(name=properties, value={initial_hosts="HOST_A[7600],HOST_B[7600]"}) The 1st operation will be transformed to /.../protocol=org.jgroups.protocols.TCPPING:add() The 2nd operation should also be transformed to the legacy resource. was: In this operation sequence, the 2nd operation fails with a NoSuchResourceException: /subsystem=jgroups/stack=tcp/protocol=TCPPING:add() /subsystem=jgroups/stack=tcp/protocol=TCPPING:write-attribute(name=properties, value={initial_hosts="HOST_A[7600],HOST_B[7600]"}) The 1st operation was redirected to protocol=org.jgroups.protocols.TCPPING:add() The 2nd operation should also be redirected to the legacy resource. > Legacy protocol write-attribute operations throw NoSuchResourceException > ------------------------------------------------------------------------ > > Key: WFLY-9146 > URL: https://issues.jboss.org/browse/WFLY-9146 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 11.0.0.Beta1 > > > In this operation sequence, the 2nd operation fails with a NoSuchResourceException: > /subsystem=jgroups/stack=tcp/protocol=TCPPING:add() > /subsystem=jgroups/stack=tcp/protocol=TCPPING:write-attribute(name=properties, value={initial_hosts="HOST_A[7600],HOST_B[7600]"}) > The 1st operation will be transformed to /.../protocol=org.jgroups.protocols.TCPPING:add() > The 2nd operation should also be transformed to the legacy resource. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9146) Legacy protocol write-attribute operations throw NoSuchResourceException

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-9146: ---------------------------------- Summary: Legacy protocol write-attribute operations throw NoSuchResourceException Key: WFLY-9146 URL: https://issues.jboss.org/browse/WFLY-9146 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 11.0.0.Alpha1 Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 11.0.0.Beta1 In this operation sequence, the 2nd operation fails with a NoSuchResourceException: /subsystem=jgroups/stack=tcp/protocol=TCPPING:add() /subsystem=jgroups/stack=tcp/protocol=TCPPING:write-attribute(name=properties, value={initial_hosts="HOST_A[7600],HOST_B[7600]"}) The 1st operation was redirected to protocol=org.jgroups.protocols.TCPPING:add() The 2nd operation should also be redirected to the legacy resource. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3120) Tests broken as part of WildFly Core 3.0.0.Beta16

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3120?page=com.atlassian.jira.plugi... ] Ken Wills updated WFCORE-3120: ------------------------------ Description: These tests were moved to wildfly-core previously. Tests shown here are going to be ignored or otherwise modified in order to get the core 3.0.0.Beta16 release integrated. org.jboss.as.test.integration.domain.elytron.SlaveHostControllerElytronAuthenticationTestCase.testSlaveRegistration org.jboss.as.test.integration.security.perimeter.CLISecurityTestCase.testConnect was: Tests shown here are going to be ignored or otherwise modified in order to get the core 3.0.0.Beta16 release integrated. org.jboss.as.test.integration.domain.elytron.SlaveHostControllerElytronAuthenticationTestCase.testSlaveRegistration org.jboss.as.test.integration.security.perimeter.CLISecurityTestCase.testConnect > Tests broken as part of WildFly Core 3.0.0.Beta16 > ------------------------------------------------- > > Key: WFCORE-3120 > URL: https://issues.jboss.org/browse/WFCORE-3120 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Ken Wills > Assignee: Farah Juma > > These tests were moved to wildfly-core previously. > Tests shown here are going to be ignored or otherwise modified in order to get the core 3.0.0.Beta16 release integrated. > org.jboss.as.test.integration.domain.elytron.SlaveHostControllerElytronAuthenticationTestCase.testSlaveRegistration > org.jboss.as.test.integration.security.perimeter.CLISecurityTestCase.testConnect -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3120) Tests broken as part of WildFly Core 3.0.0.Beta16

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3120?page=com.atlassian.jira.plugi... ] Ken Wills reassigned WFCORE-3120: --------------------------------- Assignee: Ken Wills (was: Farah Juma) > Tests broken as part of WildFly Core 3.0.0.Beta16 > ------------------------------------------------- > > Key: WFCORE-3120 > URL: https://issues.jboss.org/browse/WFCORE-3120 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Ken Wills > Assignee: Ken Wills > > These tests were moved to wildfly-core previously. > Tests shown here are going to be ignored or otherwise modified in order to get the core 3.0.0.Beta16 release integrated. > org.jboss.as.test.integration.domain.elytron.SlaveHostControllerElytronAuthenticationTestCase.testSlaveRegistration > org.jboss.as.test.integration.security.perimeter.CLISecurityTestCase.testConnect -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3120) Tests broken as part of WildFly Core 3.0.0.Beta16

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3120?page=com.atlassian.jira.plugi... ] Ken Wills updated WFCORE-3120: ------------------------------ Description: Tests shown here are going to be ignored or otherwise modified in order to get the core 3.0.0.Beta16 release integrated. org.jboss.as.test.integration.domain.elytron.SlaveHostControllerElytronAuthenticationTestCase.testSlaveRegistration org.jboss.as.test.integration.security.perimeter.CLISecurityTestCase.testConnect was: Tests shown here are going to be ignored or otherwise modified in order to get the core 3.0.0.Beta16 release integrated. org.jboss.as.test.integration.domain.elytron.SlaveHostControllerElytronAuthenticationTestCase.testSlaveRegistration org.jboss.as.test.integration.ejb.container.interceptor.security.SwitchIdentityTestCase.testClientLoginModule org.jboss.as.test.integration.ejb.container.interceptor.security.api.SwitchIdentityTestCase.testClientLoginModule org.jboss.as.test.integration.security.perimeter.CLISecurityTestCase.testConnect Failure examples: http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=113878&buildTy... > Tests broken as part of WildFly Core 3.0.0.Beta16 > ------------------------------------------------- > > Key: WFCORE-3120 > URL: https://issues.jboss.org/browse/WFCORE-3120 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Ken Wills > Assignee: Farah Juma > > Tests shown here are going to be ignored or otherwise modified in order to get the core 3.0.0.Beta16 release integrated. > org.jboss.as.test.integration.domain.elytron.SlaveHostControllerElytronAuthenticationTestCase.testSlaveRegistration > org.jboss.as.test.integration.security.perimeter.CLISecurityTestCase.testConnect -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9145) Tests broken as part of WildFly Core 3.0.0.Beta16

by Ken Wills (JIRA)

Ken Wills created WFLY-9145: ------------------------------- Summary: Tests broken as part of WildFly Core 3.0.0.Beta16 Key: WFLY-9145 URL: https://issues.jboss.org/browse/WFLY-9145 Project: WildFly Issue Type: Bug Components: Security Reporter: Ken Wills Assignee: Farah Juma Tests shown here are going to be ignored or otherwise modified in order to get the core 3.0.0.Beta16 release integrated. org.jboss.as.test.integration.domain.elytron.SlaveHostControllerElytronAuthenticationTestCase.testSlaveRegistration org.jboss.as.test.integration.ejb.container.interceptor.security.SwitchIdentityTestCase.testClientLoginModule org.jboss.as.test.integration.ejb.container.interceptor.security.api.SwitchIdentityTestCase.testClientLoginModule org.jboss.as.test.integration.security.perimeter.CLISecurityTestCase.testConnect Failure examples: http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=113878&buildTy... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3120) Tests broken as part of WildFly Core 3.0.0.Beta16

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3120?page=com.atlassian.jira.plugi... ] Ken Wills moved WFLY-9145 to WFCORE-3120: ----------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-3120 (was: WFLY-9145) Component/s: Security (was: Security) > Tests broken as part of WildFly Core 3.0.0.Beta16 > ------------------------------------------------- > > Key: WFCORE-3120 > URL: https://issues.jboss.org/browse/WFCORE-3120 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Ken Wills > Assignee: Farah Juma > > Tests shown here are going to be ignored or otherwise modified in order to get the core 3.0.0.Beta16 release integrated. > org.jboss.as.test.integration.domain.elytron.SlaveHostControllerElytronAuthenticationTestCase.testSlaveRegistration > org.jboss.as.test.integration.ejb.container.interceptor.security.SwitchIdentityTestCase.testClientLoginModule > org.jboss.as.test.integration.ejb.container.interceptor.security.api.SwitchIdentityTestCase.testClientLoginModule > org.jboss.as.test.integration.security.perimeter.CLISecurityTestCase.testConnect > Failure examples: http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=113878&buildTy... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9131) Wildfly 10.1.0 Fails to load JSF message bundle from Java class

by Bobby Bassman (JIRA)

[ https://issues.jboss.org/browse/WFLY-9131?page=com.atlassian.jira.plugin.... ] Bobby Bassman commented on WFLY-9131: ------------------------------------- Sorry, I just noticed that I had 'Security Issue' checked. This issue is not security relevant and I change the issue to reflect that fact. > Wildfly 10.1.0 Fails to load JSF message bundle from Java class > --------------------------------------------------------------- > > Key: WFLY-9131 > URL: https://issues.jboss.org/browse/WFLY-9131 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 10.1.0.Final > Environment: Windows 10 > Wildfly 10.1.0 > Reporter: Bobby Bassman > Assignee: Farah Juma > > Have a war application which deploys and runs correctly on EAP 6.4. When deploying on WIldfly 10.1.0, none of the message bundle lookups work, resulting in ???zxcv??? text on JSF pages. > This application has the following in faces-config.xml: > <application> > <locale-config> > <default-locale>en</default-locale> > <supported-locale>en_US</supported-locale> > <supported-locale>en</supported-locale> > </locale-config> > <message-bundle>com.rfdinc.efile.bp.resources.CombinedMessageResources</message-bundle> > <resource-bundle> > <base-name>com.rfdinc.efile.bp.resources.CombinedMessageResources</base-name> > <var>msg</var> > </resource-bundle> > </application> > Here, com.rfdinc.efile.bp.resources.CombinedMessageResources is a Java class which extends java.util.ResourceBundle and implements most of the methods of java.util.ResourceBundle. > This technique works correctly under EAP 6.4. Under Wildfly 10.1.0, however, none of the class methods ever get called. This was verified by placing logger messages throughout com.rfdinc.efile.bp.resources.CombinedMessageResources. > Replacing <message-bundle> and <base-name> with a 'properties' file works, but this particular Java class allows us to combine multiple property files into a single resource bundle. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9131) Wildfly 10.1.0 Fails to load JSF message bundle from Java class

by Bobby Bassman (JIRA)

[ https://issues.jboss.org/browse/WFLY-9131?page=com.atlassian.jira.plugin.... ] Bobby Bassman updated WFLY-9131: -------------------------------- Security: (was: Security Issue) Security Sensitive Issue: (was: This issue is security relevant) > Wildfly 10.1.0 Fails to load JSF message bundle from Java class > --------------------------------------------------------------- > > Key: WFLY-9131 > URL: https://issues.jboss.org/browse/WFLY-9131 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 10.1.0.Final > Environment: Windows 10 > Wildfly 10.1.0 > Reporter: Bobby Bassman > Assignee: Farah Juma > > Have a war application which deploys and runs correctly on EAP 6.4. When deploying on WIldfly 10.1.0, none of the message bundle lookups work, resulting in ???zxcv??? text on JSF pages. > This application has the following in faces-config.xml: > <application> > <locale-config> > <default-locale>en</default-locale> > <supported-locale>en_US</supported-locale> > <supported-locale>en</supported-locale> > </locale-config> > <message-bundle>com.rfdinc.efile.bp.resources.CombinedMessageResources</message-bundle> > <resource-bundle> > <base-name>com.rfdinc.efile.bp.resources.CombinedMessageResources</base-name> > <var>msg</var> > </resource-bundle> > </application> > Here, com.rfdinc.efile.bp.resources.CombinedMessageResources is a Java class which extends java.util.ResourceBundle and implements most of the methods of java.util.ResourceBundle. > This technique works correctly under EAP 6.4. Under Wildfly 10.1.0, however, none of the class methods ever get called. This was verified by placing logger messages throughout com.rfdinc.efile.bp.resources.CombinedMessageResources. > Replacing <message-bundle> and <base-name> with a 'properties' file works, but this particular Java class allows us to combine multiple property files into a single resource bundle. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2017