September 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (LOGMGR-83) Handlers should be closed on rollbacks

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-83?page=com.atlassian.jira.plugin.... ] James Perkins edited comment on LOGMGR-83 at 9/26/13 9:27 PM: -------------------------------------------------------------- Seems safe to cherry-pick on to other branches, but I'm noticing some issues with the other branches I'll sort out tomorrow. was (Author: jamezp): Seems safe to cherry-pick on to other branches, but I'm noticing some issues I'll sort out tomorrow. > Handlers should be closed on rollbacks > -------------------------------------- > > Key: LOGMGR-83 > URL: https://issues.jboss.org/browse/LOGMGR-83 > Project: JBoss Log Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: James Perkins > Assignee: James Perkins > Fix For: 1.3.3.Final, 1.4.4.Final, 1.5.2.Final, 2.0.0.Beta1 > > > Some handlers, like file handlers, might hold resources that need to be closed if a rollback occurs during configuration. The {{handler.close()}} should be invoked for this reason and any errors should be ignored. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-83) Handlers should be closed on rollbacks

by James Perkins (JIRA)

James Perkins created LOGMGR-83: ----------------------------------- Summary: Handlers should be closed on rollbacks Key: LOGMGR-83 URL: https://issues.jboss.org/browse/LOGMGR-83 Project: JBoss Log Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: James Perkins Assignee: James Perkins Fix For: 1.3.3.Final, 1.4.4.Final, 1.5.2.Final, 2.0.0.Beta1 Some handlers, like file handlers, might hold resources that need to be closed if a rollback occurs during configuration. The {{handler.close()}} should be invoked for this reason and any errors should be ignored. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1916) Deployer role within domain

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1916?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1916: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> made a comment on [bug 1012592|https://bugzilla.redhat.com/show_bug.cgi?id=1012592] WFLY-1916 seems to indicate the opposite problem from the description of this one. No matter, though. I'm going to assume this is a server-side constraints issue and dig into it. I'd change the component to Domain Management but don't want to screw up the flags. > Deployer role within domain > --------------------------- > > Key: WFLY-1916 > URL: https://issues.jboss.org/browse/WFLY-1916 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management > Reporter: Heiko Braun > Assignee: Brian Stansberry > Fix For: 8.0.0.Beta1 > > > There seems to be a problem with the deplyer role within the domain. In order to operate on doamin deployments, the deplyer requires write access to: > a) /server-group=* > b) /deployment=* > But currently only the later seems to be given. This basically reduces the deployer role to just the abillity to upload contents, but not assign them to server-groups. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2168) Forward port urn:jboss:domain:transactions:1.4 schema and parser from EAP 6

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-2168: -------------------------------------- Summary: Forward port urn:jboss:domain:transactions:1.4 schema and parser from EAP 6 Key: WFLY-2168 URL: https://issues.jboss.org/browse/WFLY-2168 Project: WildFly Issue Type: Task Components: Domain Management, Transactions Reporter: Brian Stansberry Assignee: Ivo Studensky Priority: Blocker Fix For: 8.0.0.CR1 The backport of WFLY-789 introduced a new XSD version in EAP that does not exist in WildFly. It needs to be forward ported to WildFly. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-273) KnowledgeAgent Incremental compilation fails if declared types are used in RHS

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-273: ------------------------------------- Summary: KnowledgeAgent Incremental compilation fails if declared types are used in RHS Key: DROOLS-273 URL: https://issues.jboss.org/browse/DROOLS-273 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.5.0.Final Reporter: Davide Sottara Assignee: Mark Proctor Priority: Critical Fix For: 5.5.1.Final If a newly discovered DRL contains a rule whose RHS uses a previously declared class, that rule's compilation will fail. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-274) KnowledgeAgent loops when resources are removed from a monitored folder

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-274: ------------------------------------- Summary: KnowledgeAgent loops when resources are removed from a monitored folder Key: DROOLS-274 URL: https://issues.jboss.org/browse/DROOLS-274 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Davide Sottara Assignee: Mark Proctor -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2167) resolve-path operation definition is needs RUNTIME_ONLY and READ_ONLY set

by James Perkins (JIRA)

James Perkins created WFLY-2167: ----------------------------------- Summary: resolve-path operation definition is needs RUNTIME_ONLY and READ_ONLY set Key: WFLY-2167 URL: https://issues.jboss.org/browse/WFLY-2167 Project: WildFly Issue Type: Bug Components: Domain Management Reporter: James Perkins Assignee: James Perkins Priority: Minor Fix For: 8.0.0.CR1 Domain mode requires operations be defined as {{RUNTIME_ONLY}} to for describe handler to work. This is how the {{read-operation-names}} operation finds the available operations. While the operation can still be executed, it's not listed and in CLI doesn't allow any parameters to be passed with out this flag. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBEE-143) JACC permissions added to the unchecked policy must be constructed using qualified pattern as their name

by Stefan Guilhen (JIRA)

[ https://issues.jboss.org/browse/JBEE-143?page=com.atlassian.jira.plugin.s... ] Stefan Guilhen deleted JBEE-143: -------------------------------- > JACC permissions added to the unchecked policy must be constructed using qualified pattern as their name > --------------------------------------------------------------------------------------------------------- > > Key: JBEE-143 > URL: https://issues.jboss.org/browse/JBEE-143 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Reporter: Stefan Guilhen > Assignee: Stefan Guilhen > > As reported by [~jcacek]: > JACC 1.1 specification, chapter 3.1.3.1 Translating security-constraint Elements says: > {panel} > A WebResourcePermission and a WebUserDataPermission must be added to > the unchecked policy statements for each url-pattern in the deployment > descriptor and the default pattern, "/", that is not combined by the web- > resource-collection elements of the deployment descriptor with every > HTTP method value. The permission objects must be constructed using the > *qualified pattern* as their name and with actions represented by an HTTP method > exception list that identifies (as defined in “HTTP Method Exception List”) all the > HTTP methods that do not occur in combination with the pattern.The resulting > permissions must be added to the unchecked policy statements by calling the > addToUncheckedPolicy method on the PolicyConfiguration object. > {panel} > but the class WarJaccService doesn't use qualified patterns (around line 170 in source code): > {code} > String excludedString = "!" + getCommaSeparatedString(httpMethods); > WebResourcePermission wrp1 = new WebResourcePermission(info.pattern, excludedString); > WebUserDataPermission wudp1 = new WebUserDataPermission(info.pattern, excludedString); > {code} -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBEE-144) JACC 1.1 implementation must use exception list instead of missing method list for HTTP methods in the unchecked permissions

by Stefan Guilhen (JIRA)

[ https://issues.jboss.org/browse/JBEE-144?page=com.atlassian.jira.plugin.s... ] Stefan Guilhen deleted JBEE-144: -------------------------------- > JACC 1.1 implementation must use exception list instead of missing method list for HTTP methods in the unchecked permissions > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBEE-144 > URL: https://issues.jboss.org/browse/JBEE-144 > Project: JBoss JavaEE Spec APIs > Issue Type: Bug > Reporter: Stefan Guilhen > Assignee: Stefan Guilhen > > As reported by [~jcacek]: > The method {{org.jboss.as.web.security.WarJaccService.PatternInfo.getMissingMethods()}} which subtracts current methods set from the "big 7" is used for constructing some unchecked permissions. > The method exception list (i.e. exclamation mark followed by current methods) must be used instead - as defined in section 3.1.3.1 of JACC 1.1 specification. > The specification says: > {panel} > h4.HTTP Method Exception List > An HTTP method exception list is used to represent, by set difference, a non- > enumerable subset of the set of all possible HTTP methods. An exception list > respresents the subset of the complete set of HTTP methods formed by subtracting > the methods named in the exception list from the complete set. > An exception list is distinguished by its first character, which must be the > exclaimation point (i.e., “!”) character. A comma seperated list of one or more > HTTP method names must follow the exclaimation point. > {panel} -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBEE-144) JACC 1.1 implementation must use exception list instead of missing method list for HTTP methods in the unchecked permissions

by Stefan Guilhen (JIRA)

Stefan Guilhen created JBEE-144: ----------------------------------- Summary: JACC 1.1 implementation must use exception list instead of missing method list for HTTP methods in the unchecked permissions Key: JBEE-144 URL: https://issues.jboss.org/browse/JBEE-144 Project: JBoss JavaEE Spec APIs Issue Type: Bug Components: jboss-jacc-api Affects Versions: JavaEE 6 Spec APIs 3.0.2.Final Reporter: Stefan Guilhen Assignee: Stefan Guilhen Fix For: JavaEE Spec APIs 3.0.3.Final As reported by [~jcacek]: The method {{org.jboss.as.web.security.WarJaccService.PatternInfo.getMissingMethods()}} which subtracts current methods set from the "big 7" is used for constructing some unchecked permissions. The method exception list (i.e. exclamation mark followed by current methods) must be used instead - as defined in section 3.1.3.1 of JACC 1.1 specification. The specification says: {panel} h4.HTTP Method Exception List An HTTP method exception list is used to represent, by set difference, a non- enumerable subset of the set of all possible HTTP methods. An exception list respresents the subset of the complete set of HTTP methods formed by subtracting the methods named in the exception list from the complete set. An exception list is distinguished by its first character, which must be the exclaimation point (i.e., “!”) character. A comma seperated list of one or more HTTP method names must follow the exclaimation point. {panel} -- 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, 9 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 September 2013