March 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2858) misc. decision table bugs and improvements

by Wolfgang Laun (JIRA)

misc. decision table bugs and improvements ------------------------------------------ Key: JBRULES-2858 URL: https://issues.jboss.org/browse/JBRULES-2858 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-decisiontables Affects Versions: 5.1.1.FINAL Reporter: Wolfgang Laun Assignee: Mark Proctor Fix For: 5.2.0.M2 RuleTable and column headers (CONDITION, ACTION,...) are ignored when written with a leading space. Errors are reported in row & column numbers; this should be done using cell names. Duplicate columns for rule attributes are silently ignored; there should be a diagnostic. NumberFormatException thrown on bad integer must be caught and result in a proper diagnostic. Description entry is notwritten into the generated DRL. Some attributes cannot be produced: lock-on-active, etc. NPE thrown for certain entries Documentation is rather "off" in several places. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (SECURITY-31) White Paper on JMX Security

by Anil Saldhana (JIRA)

White Paper on JMX Security --------------------------- Key: SECURITY-31 URL: http://jira.jboss.com/jira/browse/SECURITY-31 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: White Papers Reporter: Anil Saldhana Assigned To: Anil Saldhana There is a need for a simple technical white paper that talks about the various scenarios involved in security jmx in JBoss. This includes the jmx consoles as well as the invokers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-9140) Incorrect value for boolean parameter

by Brian Stansberry (JIRA)

Incorrect value for boolean parameter ------------------------------------- Key: JBAS-9140 URL: https://issues.jboss.org/browse/JBAS-9140 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: CLI Reporter: Brian Stansberry Assignee: Alexey Loubyansky With the latest from master, this operation: /socket-binding-group=standard-sockets/socket-binding=http:write-attribute(name=fixed-port,value=true) results in this operation on the server (incorrect value): { "operation" => "write-attribute", "name" => "fixed-port", "value" => false, "address" => [ ("socket-binding-group" => "standard-sockets"), ("socket-binding" => "http") ] } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (JBAS-9179) Upgrade jboss-dmr to 1.0.0.Beta4

by Brian Stansberry (JIRA)

Upgrade jboss-dmr to 1.0.0.Beta4 -------------------------------- Key: JBAS-9179 URL: https://issues.jboss.org/browse/JBAS-9179 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.Beta2 Need a 1.0.0.Beta4 release to pick up http://github.com/jbossas/jboss-dmr/compare/39829c8...43c6696 and allow fix for JBAS-9140. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-8204) Deployment via a deployment plan

by Brian Stansberry (JIRA)

Deployment via a deployment plan -------------------------------- Key: JBAS-8204 URL: https://jira.jboss.org/browse/JBAS-8204 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.M2 I want us to have some sort of deployment plan notion in our deployment API so users can specify in a document how a rolling upgrade should occur, e.g. here's the new deployment(s), first quiesce this set of servers, then upgrade, roll on to this set of servers, etc. Basically describe in a document the set of operations that are meant to be atomic. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (SECURITY-561) JBossResponseContext getResult strips multiple obligations from the evaluation response.

by Brian Krisler (JIRA)

JBossResponseContext getResult strips multiple obligations from the evaluation response. ---------------------------------------------------------------------------------------- Key: SECURITY-561 URL: https://issues.jboss.org/browse/SECURITY-561 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: PicketBox Affects Versions: 2.0.2.CR12 Environment: N/A Reporter: Brian Krisler Assignee: Anil Saldhana The getResult() method in JBossResponseContext prevents multiple Obligations from getting returned to the PEP. The code block: //Obligations Set<Obligation> obligationsSet = result.getObligations(); if(obligationsSet != null) { for(Obligation obl:obligationsSet) { ObligationType obType = new ObligationType(); obType.setObligationId(obl.getId().toASCIIString()); obType.setFulfillOn(EffectType.fromValue(Result.DECISIONS[obl.getFulfillOn()])); ObligationsType obligationsType = new ObligationsType(); obligationsType.getObligation().add(obType); resultType.setObligations(obligationsType); } } Causes the obligations to constantly get overwritten with the last one read in. --> resultType.setObligations(obligationsType) To fix, do something more like: // Obligations Set<Obligation> obligationsSet = result.getObligations(); if (obligationsSet != null && obligationsSet.size() > 0) { ObligationsType obligationsType = new ObligationsType(); for (Obligation obl : obligationsSet) { ObligationType obType = new ObligationType(); obType.setObligationId(obl.getId().toASCIIString()); obType.setFulfillOn(EffectType.fromValue(Result.DECISIONS[obl.getFulfillOn()])); obligationsType.getObligation().add(obType); } resultType.setObligations(obligationsType); } -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (SECURITY-566) LDAP Policy/Attribute Locator should refresh based on the modifyTimeStamp attribute of ldap entry

by Anil Saldhana (JIRA)

LDAP Policy/Attribute Locator should refresh based on the modifyTimeStamp attribute of ldap entry ------------------------------------------------------------------------------------------------- Key: SECURITY-566 URL: https://issues.jboss.org/browse/SECURITY-566 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossXACML Affects Versions: jbossxacml_2.0.5.final Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: jbossxacml_2.0.6.Final LDAP defines the modifyTimeStamp attribute to handle the updates to ldap entries. This can be a valuable piece of information for the ldap policy/attribute locators to refresh their data. This should be a configurable value added feature. Not the default. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2833) DroolsCompilerAntTask should scan for drools.package first

by Tihomir Surdilovic (JIRA)

DroolsCompilerAntTask should scan for drools.package first ---------------------------------------------------------- Key: JBRULES-2833 URL: https://issues.jboss.org/browse/JBRULES-2833 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-ant Affects Versions: 5.1.1.FINAL Reporter: Tihomir Surdilovic Assignee: Tihomir Surdilovic Fix For: 5.2.0.M1 DroolsCompilerAntTask should scan for drools.package first, before other rule resources -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBWEB-95) Provide a com.sun.net.httpserver.HttpServerProvider implementation

by Scott M Stark (JIRA)

Provide a com.sun.net.httpserver.HttpServerProvider implementation ------------------------------------------------------------------ Key: JBWEB-95 URL: http://jira.jboss.com/jira/browse/JBWEB-95 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tomcat Module Reporter: Scott M Stark Assigned To: Mladen Turk To plug jbossweb into jdk6, we need a com.sun.net.httpserver.HttpServerProvider implementation http://java.sun.com/javase/6/docs/jre/api/net/httpserver/spec/com/sun/net... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
12
0 / 0

[JBoss JIRA] Created: (JBWEB-183) "Wrong" encoding of ObjectNames for connector mbeans

by Dimitris Andreadis (JIRA)

"Wrong" encoding of ObjectNames for connector mbeans ---------------------------------------------------- Key: JBWEB-183 URL: https://jira.jboss.org/browse/JBWEB-183 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Components: Tomcat Affects Versions: JBossWeb-2.0.0.GA_CP10 Reporter: Dimitris Andreadis Assignee: Remy Maucherat Looking into this bug report: JBPAPP-3050: I think the "problem" is in tomcat/jbossweb. When it creates the JMX ObjectNames for connector MBeans, e.g. look at: http://anonsvn.jboss.org/repos/jbossweb/tags/JBOSSWEB_2_0_0_GA_CP15/src/s... ... public String getName() { String encodedAddr = ""; if (getAddress() != null) { encodedAddr = "" + getAddress(); if (encodedAddr.startsWith("/")) encodedAddr = encodedAddr.substring(1); encodedAddr = URLEncoder.encode(encodedAddr) + "-"; <=== HERE } return ("http-" + encodedAddr + endpoint.getPort()) ... Basically it encodes the address and so http-localhost/127.0.0.1-8080 becomes http-localhost%2F127.0.0.1-8080 If you address the MBean like this, it is visible to any JMX subystem (twiddle, SNMP, concole, etc.), so that could be considered a valid workaround: jboss.web:type=ThreadPool,name=http-localhost%2F127.0.0.1-8080 I guess tomcat/jboss should be using javax.management.ObjectName.quote(String) to encode the name: http://download.oracle.com/javase/1.5.0/docs/api/javax/management/ObjectN... No big deal. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
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 March 2011