July 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9150) The enable-elytron.cli scripts are using an invalid domain wide /core-service=management/access=identity resource

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-9150: -------------------------------------- Summary: The enable-elytron.cli scripts are using an invalid domain wide /core-service=management/access=identity resource Key: WFLY-9150 URL: https://issues.jboss.org/browse/WFLY-9150 Project: WildFly Issue Type: Bug Components: Domain Management, Security Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Blocker See WFCORE-3121. This call in the enable-elytron.cli scripts: {code} /core-service=management/access=identity:add(security-domain=ManagementDomain) {code} needs to be {code} /host=master/core-service=management/access=identity:add(security-domain=ManagementDomain) {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3122) Elytron is registering resource /core-service=management/access=identity on a HostController

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3122: ---------------------------------------- Summary: Elytron is registering resource /core-service=management/access=identity on a HostController Key: WFCORE-3122 URL: https://issues.jboss.org/browse/WFCORE-3122 Project: WildFly Core Issue Type: Bug Components: Domain Management, Security Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Blocker Fix For: 3.0.0.CR1 The Elytron integration added a resource registration for /core-service=management/access=identity on an HC. It should only be registered at /host=*/core-service=management/access=identity The domain-wide /core-service=management resource MUST NOT HAVE CHILDREN REGISTERED other than access-authorization. It is not the place to configure HC-specific behavior. I see use of this resource in enable-elytron.cli scripts used to configure the testsuite. At least in the one in WF full's testsuite/shared; I'm guessing elsewhere too. That must be changed. If use of this domain-wide resource has ended up in any docs those must be corrected. [~dlofthouse] FYI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3121) Elytron is registering resource /core-service=management/access=identity on a HostController

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3121?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3121: ------------------------------------- Fix Version/s: 3.0.0.CR1 > Elytron is registering resource /core-service=management/access=identity on a HostController > -------------------------------------------------------------------------------------------- > > Key: WFCORE-3121 > URL: https://issues.jboss.org/browse/WFCORE-3121 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 3.0.0.CR1 > > > The Elytron integration added a resource registration for /core-service=management/access=identity on an HC. It should only be registered at /host=*/core-service=management/access=identity > The domain-wide /core-service=management resource MUST NOT HAVE CHILDREN REGISTERED other than access-authorization. It is not the place to configure HC-specific behavior. > I see use of this resource in enable-elytron.cli scripts used to configure the testsuite. At least in the one in WF full's testsuite/shared; I'm guessing elsewhere too. That must be changed. > If use of this domain-wide resource has ended up in any docs those must be corrected. > [~dlofthouse] FYI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3121) Elytron is registering resource /core-service=management/access=identity on a HostController

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3121: ---------------------------------------- Summary: Elytron is registering resource /core-service=management/access=identity on a HostController Key: WFCORE-3121 URL: https://issues.jboss.org/browse/WFCORE-3121 Project: WildFly Core Issue Type: Bug Components: Domain Management, Security Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Blocker The Elytron integration added a resource registration for /core-service=management/access=identity on an HC. It should only be registered at /host=*/core-service=management/access=identity The domain-wide /core-service=management resource MUST NOT HAVE CHILDREN REGISTERED other than access-authorization. It is not the place to configure HC-specific behavior. I see use of this resource in enable-elytron.cli scripts used to configure the testsuite. At least in the one in WF full's testsuite/shared; I'm guessing elsewhere too. That must be changed. If use of this domain-wide resource has ended up in any docs those must be corrected. [~dlofthouse] FYI. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9148) Clustering subsystem use of deprecated XML writer registration

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-9148: ---------------------------------- Summary: Clustering subsystem use of deprecated XML writer registration Key: WFLY-9148 URL: https://issues.jboss.org/browse/WFLY-9148 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 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9149) Clustering subsystem use of deprecated XML writer registration

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-9149: ---------------------------------- Summary: Clustering subsystem use of deprecated XML writer registration Key: WFLY-9149 URL: https://issues.jboss.org/browse/WFLY-9149 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 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9147) POJO WS not defaulting to Undertow default-security-domain

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/WFLY-9147?page=com.atlassian.jira.plugin.... ] Alessio Soldano reassigned WFLY-9147: ------------------------------------- Assignee: Jim Ma (was: Alessio Soldano) > POJO WS not defaulting to Undertow default-security-domain > ---------------------------------------------------------- > > Key: WFLY-9147 > URL: https://issues.jboss.org/browse/WFLY-9147 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 11.0.0.Alpha1 > Reporter: Brad Maxwell > Assignee: Jim Ma > > A POJO WS should default to the Undertow default-security-domain just as an EJB WS defaults to the default-security-domain defined in the ejb3 subsystem. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9147) POJO WS not defaulting to Undertow default-security-domain

by Brad Maxwell (JIRA)

Brad Maxwell created WFLY-9147: ---------------------------------- Summary: POJO WS not defaulting to Undertow default-security-domain Key: WFLY-9147 URL: https://issues.jboss.org/browse/WFLY-9147 Project: WildFly Issue Type: Bug Components: Web Services Affects Versions: 11.0.0.Alpha1 Reporter: Brad Maxwell Assignee: Alessio Soldano A POJO WS should default to the Undertow default-security-domain just as an EJB WS defaults to the default-security-domain defined in the ejb3 subsystem. -- 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: {noformat} /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]"}) {noformat} 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 will be transformed to /.../protocol=org.jgroups.protocols.TCPPING:add() The 2nd operation should also be transformed 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: > {noformat} > /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]"}) > {noformat} > 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-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: com.rfdinc.efile.bp.resources.zip > 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, com.rfdinc.efile.bp.resources.zip > > > 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