December 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2603) The CLI should be capable of updating/adding/removing indivisual items in a list

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2603?page=com.atlassian.jira.plugin.... ] Tomaz Cerar closed WFLY-2603. ----------------------------- Assignee: Tomaz Cerar (was: Alexey Loubyansky) Resolution: Duplicate Issue Duplicate of WFLY-548 > The CLI should be capable of updating/adding/removing indivisual items in a list > -------------------------------------------------------------------------------- > > Key: WFLY-2603 > URL: https://issues.jboss.org/browse/WFLY-2603 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: CLI > Affects Versions: 8.0.0.Beta1 > Environment: WildFly current build > Reporter: Tom Fonteyne > Assignee: Tomaz Cerar > > Here is an example using a security domain. The issue is of course valid for all locations where a list of objects is expected. > (for brevity, I only list a couple of options) > /subsystem=security/security-domain=LdapRealm:add(cache-type=default) > /subsystem=security/security-domain=LdapRealm/authentication=classic:add(login-modules=[{"code" => "LdapExtended", "flag" => "required", "module-options" => {"java.naming.provider.url" => "ldap://server.redhat.com:389/", "roleRecursion" => "0" }}]) > There is currently no way to change a *single* option in that list. You can only remove the attribute "module-options" completely and re-add it. > We need something like: > /subsystem=security/security-domain=LdapRealm/authentication=classic/login-module=LdapExtended:write-list-attribute(name=module-options,value={"roleRecursion" => "1"}) > and similarly for "read" and "undefine" methods -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2603) The CLI should be capable of updating/adding/removing indivisual items in a list

by Tom Fonteyne (JIRA)

Tom Fonteyne created WFLY-2603: ---------------------------------- Summary: The CLI should be capable of updating/adding/removing indivisual items in a list Key: WFLY-2603 URL: https://issues.jboss.org/browse/WFLY-2603 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Components: CLI Affects Versions: 8.0.0.Beta1 Environment: WildFly current build Reporter: Tom Fonteyne Assignee: Alexey Loubyansky Here is an example using a security domain. The issue is of course valid for all locations where a list of objects is expected. (for brevity, I only list a couple of options) /subsystem=security/security-domain=LdapRealm:add(cache-type=default) /subsystem=security/security-domain=LdapRealm/authentication=classic:add(login-modules=[{"code" => "LdapExtended", "flag" => "required", "module-options" => {"java.naming.provider.url" => "ldap://server.redhat.com:389/", "roleRecursion" => "0" }}]) There is currently no way to change a *single* option in that list. You can only remove the attribute "module-options" completely and re-add it. We need something like: /subsystem=security/security-domain=LdapRealm/authentication=classic/login-module=LdapExtended:write-list-attribute(name=module-options,value={"roleRecursion" => "1"}) and similarly for "read" and "undefine" methods -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2604) The CLI should be capable of updating/adding/removing indivisual items in a list

by Tom Fonteyne (JIRA)

Tom Fonteyne created WFLY-2604: ---------------------------------- Summary: The CLI should be capable of updating/adding/removing indivisual items in a list Key: WFLY-2604 URL: https://issues.jboss.org/browse/WFLY-2604 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Components: CLI Affects Versions: 8.0.0.Beta1 Environment: WildFly current build Reporter: Tom Fonteyne Assignee: Alexey Loubyansky Here is an example using a security domain. The issue is of course valid for all locations where a list of objects is expected. (for brevity, I only list a couple of options) /subsystem=security/security-domain=LdapRealm:add(cache-type=default) /subsystem=security/security-domain=LdapRealm/authentication=classic:add(login-modules=[{"code" => "LdapExtended", "flag" => "required", "module-options" => {"java.naming.provider.url" => "ldap://server.redhat.com:389/", "roleRecursion" => "0" }}]) There is currently no way to change a *single* option in that list. You can only remove the attribute "module-options" completely and re-add it. We need something like: /subsystem=security/security-domain=LdapRealm/authentication=classic/login-module=LdapExtended:write-list-attribute(name=module-options,value={"roleRecursion" => "1"}) and similarly for "read" and "undefine" methods -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1752) Concurrent message headers modification causes that message is never sent

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1752?page=com.atlassian.jira.plugin.... ] Bela Ban edited comment on JGRP-1752 at 12/4/13 6:27 AM: --------------------------------------------------------- https://github.com/belaban/JGroups/commit/1ded73104b701b448f06fb0a8eb2077... was (Author: belaban): 1ded73104b701b448f06fb0a8eb2077c0fbb0347 > Concurrent message headers modification causes that message is never sent > ------------------------------------------------------------------------- > > Key: JGRP-1752 > URL: https://issues.jboss.org/browse/JGRP-1752 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4.1 > Reporter: Radim Vansa > Assignee: Bela Ban > Fix For: 3.4.2, 3.5 > > > Under some circumstances the TP protocol may try to add the TP header to message twice concurrently. > This happens for example when the stable message triggers retransmission while the message has been sent right now. > This may result in ArrayOutOfBoundException in Headers._putHeader and/or subsequent NullPointerException in Headers.size(). The retransmission attempt always fails, the message is never delivered. Moreover, keeping this (and possibly following) messages in the transmission table can lead to OOME. -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1752) Concurrent message headers modification causes that message is never sent

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1752?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1752. ---------------------------- Resolution: Done 1ded73104b701b448f06fb0a8eb2077c0fbb0347 > Concurrent message headers modification causes that message is never sent > ------------------------------------------------------------------------- > > Key: JGRP-1752 > URL: https://issues.jboss.org/browse/JGRP-1752 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4.1 > Reporter: Radim Vansa > Assignee: Bela Ban > Fix For: 3.4.2, 3.5 > > > Under some circumstances the TP protocol may try to add the TP header to message twice concurrently. > This happens for example when the stable message triggers retransmission while the message has been sent right now. > This may result in ArrayOutOfBoundException in Headers._putHeader and/or subsequent NullPointerException in Headers.size(). The retransmission attempt always fails, the message is never delivered. Moreover, keeping this (and possibly following) messages in the transmission table can lead to OOME. -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2602) ValidatorFactory#close should be closed undeploy of application

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/WFLY-2602?page=com.atlassian.jira.plugin.... ] Hardy Ferentschik updated WFLY-2602: ------------------------------------ Description: During the undeploy of an application _ValidatorFactory#close_ should be called to allow Hibernate Validator to release resources. This should probably happen in _ BeanValidationFactoryDeployer#undeploy()_. (was: During the undeploy of an application _ValidatorFactory#close_ should be called to allow Hibernate Validator to release resources. This should probably happen in {{ BeanValidationFactoryDeployer#undeploy()}}.) > ValidatorFactory#close should be closed undeploy of application > --------------------------------------------------------------- > > Key: WFLY-2602 > URL: https://issues.jboss.org/browse/WFLY-2602 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Hardy Ferentschik > > During the undeploy of an application _ValidatorFactory#close_ should be called to allow Hibernate Validator to release resources. This should probably happen in _ BeanValidationFactoryDeployer#undeploy()_. -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2602) ValidatorFactory#close should be closed undeploy of application

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/WFLY-2602?page=com.atlassian.jira.plugin.... ] Hardy Ferentschik updated WFLY-2602: ------------------------------------ Summary: ValidatorFactory#close should be closed undeploy of application (was: ValidatorFactory#close should be closed un undeploy) > ValidatorFactory#close should be closed undeploy of application > --------------------------------------------------------------- > > Key: WFLY-2602 > URL: https://issues.jboss.org/browse/WFLY-2602 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Hardy Ferentschik > > During the undeploy of an application _ValidatorFactory#close_ should be called to allow Hibernate Validator to release resources. This should probably happen in {{ BeanValidationFactoryDeployer#undeploy()}}. -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2602) ValidatorFactory#close should be closed undeploy of application

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/WFLY-2602?page=com.atlassian.jira.plugin.... ] Hardy Ferentschik updated WFLY-2602: ------------------------------------ Description: During the undeploy of an application _ValidatorFactory#close_ should be called to allow Hibernate Validator to release resources. This should probably happen in _BeanValidationFactoryDeployer#undeploy()_. (was: During the undeploy of an application _ValidatorFactory#close_ should be called to allow Hibernate Validator to release resources. This should probably happen in _ BeanValidationFactoryDeployer#undeploy()_.) > ValidatorFactory#close should be closed undeploy of application > --------------------------------------------------------------- > > Key: WFLY-2602 > URL: https://issues.jboss.org/browse/WFLY-2602 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Hardy Ferentschik > > During the undeploy of an application _ValidatorFactory#close_ should be called to allow Hibernate Validator to release resources. This should probably happen in _BeanValidationFactoryDeployer#undeploy()_. -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2602) ValidatorFactory#close should be closed un undeploy

by Hardy Ferentschik (JIRA)

Hardy Ferentschik created WFLY-2602: --------------------------------------- Summary: ValidatorFactory#close should be closed un undeploy Key: WFLY-2602 URL: https://issues.jboss.org/browse/WFLY-2602 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Hardy Ferentschik During the undeploy of an application _ValidatorFactory#close_ should be called to allow Hibernate Validator to release resources. This should probably happen in {{ BeanValidationFactoryDeployer#undeploy()}}. -- 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

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2601) Upgrade Hibernate Validator to 5.1.0

by Hardy Ferentschik (JIRA)

Hardy Ferentschik created WFLY-2601: --------------------------------------- Summary: Upgrade Hibernate Validator to 5.1.0 Key: WFLY-2601 URL: https://issues.jboss.org/browse/WFLY-2601 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 8.0.0.Beta1 Reporter: Hardy Ferentschik Fix For: 8.0.0.Final Once available the Hibernate Validator dependency should be upgraded to 5.1.0.Final to avoid leakage of deployment classes during redeploys - see https://hibernate.atlassian.net/browse/HV-838 -- 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

10 years, 7 months

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 2013