December 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6223) org.jboss.as.protocol.ProtocolChannelClient needs to support client socket bind address config

by William DeCoste (JIRA)

William DeCoste created AS7-6223: ------------------------------------ Summary: org.jboss.as.protocol.ProtocolChannelClient needs to support client socket bind address config Key: AS7-6223 URL: https://issues.jboss.org/browse/AS7-6223 Project: Application Server 7 Issue Type: Feature Request Components: CLI Affects Versions: 7.1.0.Final Reporter: William DeCoste Assignee: William DeCoste OpenShift requires that the client socket bind address be set to the OPENSHIFT_INTENRAL_IP loopback. ProtocolChannelClient currently does not support config for the bind address. connect(..) should be calling return endpoint.connect("remote", bindAddress, destAddress, builder.getMap(), actualHandler, sslContext); instead of return endpoint.connect(uri, builder.getMap(), actualHandler, sslContext); and expose bindAddress config -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-6222) JCA workmanager and bootstrap-context "name" attributes should not support expressions

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-6222: ------------------------------------- Summary: JCA workmanager and bootstrap-context "name" attributes should not support expressions Key: AS7-6222 URL: https://issues.jboss.org/browse/AS7-6222 Project: Application Server 7 Issue Type: Sub-task Components: Domain Management, JCA Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.2.0.Alpha1 These "name" attributes represent part of the address of a resource. Resource address elements cannot support expressions, because their value needs to be resolvable 1) before all system property values are known 2) on the master host controller, which may have different resolution sources from other HCs or the servers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-6222) JCA workmanager and bootstrap-context "name" attributes should not support expressions

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6222?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-6222: --------------------------------------- I plan to fix this for 7.2 even if we don't fix the parent issue, because any use of an expression for these is broken. > JCA workmanager and bootstrap-context "name" attributes should not support expressions > -------------------------------------------------------------------------------------- > > Key: AS7-6222 > URL: https://issues.jboss.org/browse/AS7-6222 > Project: Application Server 7 > Issue Type: Sub-task > Components: Domain Management, JCA > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 7.2.0.Alpha1 > > > These "name" attributes represent part of the address of a resource. Resource address elements cannot support expressions, because their value needs to be resolvable > 1) before all system property values are known > 2) on the master host controller, which may have different resolution sources from other HCs or the servers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-6221) JCA workmanager and bootstrap-context "name" attributes are read-write

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-6221?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-6221: --------------------------------------- I put a 7.3 Fix Version on this because I don't want to deal with compatibility issues at this point in the 7.2 cycle. If it turns out this only became read-write during 7.2 development, then we should fix it in 7.2. > JCA workmanager and bootstrap-context "name" attributes are read-write > ---------------------------------------------------------------------- > > Key: AS7-6221 > URL: https://issues.jboss.org/browse/AS7-6221 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management, JCA > Reporter: Brian Stansberry > Assignee: Stefano Maestri > Fix For: 7.3.0.Alpha1 > > > The "name" attributes for workmanager and bootstrap-context resources are read-write and should be read-only. They represent the value of the last element of the resource address and thus should not be changed independently of adding/removing the resource. > Where we find these "name" attributes we've been converting their handling such that when they get registered in ManagementResourceRegistration, it is done like this: > mrr.registerReadOnlyAttribute(NAME, ReadResourceNameOperationStepHandler.INSTANCE); > where "NAME" is an AttributeDefinition. > With that, the "add" handler for the resource shouldn't store the name in the model. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-6221) JCA workmanager and bootstrap-context "name" attributes are read-write

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-6221: ------------------------------------- Summary: JCA workmanager and bootstrap-context "name" attributes are read-write Key: AS7-6221 URL: https://issues.jboss.org/browse/AS7-6221 Project: Application Server 7 Issue Type: Bug Components: Domain Management, JCA Reporter: Brian Stansberry Assignee: Stefano Maestri Fix For: 7.3.0.Alpha1 The "name" attributes for workmanager and bootstrap-context resources are read-write and should be read-only. They represent the value of the last element of the resource address and thus should not be changed independently of adding/removing the resource. Where we find these "name" attributes we've been converting their handling such that when they get registered in ManagementResourceRegistration, it is done like this: mrr.registerReadOnlyAttribute(NAME, ReadResourceNameOperationStepHandler.INSTANCE); where "NAME" is an AttributeDefinition. With that, the "add" handler for the resource shouldn't store the name in the model. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-6192) Upgrade JGroups to 3.2.5.Final

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/AS7-6192?page=com.atlassian.jira.plugin.s... ] Paul Ferraro commented on AS7-6192: ----------------------------------- This version isn't yet supported by Infinispan (as of 5.2.0.Beta6). > Upgrade JGroups to 3.2.5.Final > ------------------------------ > > Key: AS7-6192 > URL: https://issues.jboss.org/browse/AS7-6192 > Project: Application Server 7 > Issue Type: Component Upgrade > Components: Clustering > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 7.2.0.Alpha1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-6220) WebJASPIAuthenticator ignores descriptor roles if GroupPrincipalCallback is not empty

by Stefan Guilhen (JIRA)

Stefan Guilhen created AS7-6220: ----------------------------------- Summary: WebJASPIAuthenticator ignores descriptor roles if GroupPrincipalCallback is not empty Key: AS7-6220 URL: https://issues.jboss.org/browse/AS7-6220 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.1.3.Final (EAP) Reporter: Stefan Guilhen Assignee: Stefan Guilhen Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP) The fix for AS7-5735 introduced a regression in the TCK tests because now the WebJASPIAuthenticator is ignoring the descriptor roles when a non-empty GroupPrincipalCallback is returned from the JASPI authentication. The authenticator must add the descriptor roles to the set of roles retrieved from the GroupPrincipalCallback -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-6068) jar file system is broken again (regression)

by Alvin Thompson (JIRA)

[ https://issues.jboss.org/browse/AS7-6068?page=com.atlassian.jira.plugin.s... ] Alvin Thompson edited comment on AS7-6068 at 12/19/12 12:04 PM: ---------------------------------------------------------------- Test case? Add a security provider jar to your war/ear and attempt to use it. I used bouncycastle but I imagine it doesn't make a difference. Before the security provider can load, the jar needs to be validated. This is done by accessing the files through the jar file system (provided by jboss) and inspecting them (I imagine it does something like comparing the file's checksum to a known value). Apparently, the jar file system does not properly handle the "jar within a jar" scenario. Please look at the related bug for details. was (Author: alvint): Test case? Add a security provider jar to your war/ear and attempt to use it. I used bouncycastle but I imagine it doesn't make a difference. Before the security provider can load, the jar needs to be validated. This is done by accessing the files through the jar file system (provided by jboss) and inspecting them (I imagine it does something like comparing the file's checksum to a known value). Apparently, the jar file system does not properly handle the "jar within a jar" scenario. > jar file system is broken again (regression) > -------------------------------------------- > > Key: AS7-6068 > URL: https://issues.jboss.org/browse/AS7-6068 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: 7.1.1.Final > Reporter: Alvin Thompson > Assignee: JBoss SET > Priority: Critical > > Similar to issue JBAS-7882, you cannot bundle a security provider in a WAR/EAR, because JBOSS's jar file system becomes confused when there are JARs nested in other JARs/WARs/EARs, which is pretty much always. > This was supposedly fixed in previous versions, but it's back in 7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-6068) jar file system is broken again (regression)

by Alvin Thompson (JIRA)

[ https://issues.jboss.org/browse/AS7-6068?page=com.atlassian.jira.plugin.s... ] Alvin Thompson commented on AS7-6068: ------------------------------------- Test case? Add a security provider jar to your war/ear and attempt to use it. I used bouncycastle but I imagine it doesn't make a difference. Before the security provider can load, the jar needs to be validated. This is done by accessing the files through the jar file system (provided by jboss) and inspecting them (I imagine it does something like comparing the file's checksum to a known value). Apparently, the jar file system does not properly handle the "jar within a jar" scenario. > jar file system is broken again (regression) > -------------------------------------------- > > Key: AS7-6068 > URL: https://issues.jboss.org/browse/AS7-6068 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: 7.1.1.Final > Reporter: Alvin Thompson > Assignee: JBoss SET > Priority: Critical > > Similar to issue JBAS-7882, you cannot bundle a security provider in a WAR/EAR, because JBOSS's jar file system becomes confused when there are JARs nested in other JARs/WARs/EARs, which is pretty much always. > This was supposedly fixed in previous versions, but it's back in 7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-6218) allow expressions in the infinispan subsystem

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/AS7-6218?page=com.atlassian.jira.plugin.s... ] Radoslav Husar reassigned AS7-6218: ----------------------------------- Assignee: Richard Achmatowicz (was: Radoslav Husar) > allow expressions in the infinispan subsystem > --------------------------------------------- > > Key: AS7-6218 > URL: https://issues.jboss.org/browse/AS7-6218 > Project: Application Server 7 > Issue Type: Sub-task > Components: Clustering, Domain Management > Reporter: Jeff Mesnil > Assignee: Richard Achmatowicz > Fix For: 7.2.0.Alpha1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2012