[
https://jira.jboss.org/jira/browse/SECURITY-487?page=com.atlassian.jira.p...
]
Anil Saldhana updated SECURITY-487:
-----------------------------------
Component/s: JBossSX
Fix Version/s: JBossSecurity_2.0.4.SP4
PicketBox_v3_0_beta4
Affects Version/s: PicketBox_v3_0_beta3
JBossSecurity_2.0.4.SP3
Assignee: Stefan Guilhen (was: Anil Saldhana)
JBossMappingManager uses incorrect (misleading) Logger
------------------------------------------------------
Key: SECURITY-487
URL:
https://jira.jboss.org/jira/browse/SECURITY-487
Project: PicketBox (JBoss Security and Identity Management)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JBossSX
Affects Versions: JBossSecurity_2.0.4.SP3, PicketBox_v3_0_beta3
Environment: JBoss AS Trunk
Reporter: jaikiran pai
Assignee: Stefan Guilhen
Priority: Minor
Fix For: JBossSecurity_2.0.4.SP4, PicketBox_v3_0_beta4
While debugging an issue (through logs), I realized after much fighting, that
JBossMappingManager uses an incorrect logger:
public class JBossMappingManager implements MappingManager
{
protected static final Logger log = Logger.getLogger(JBossSecurityContext.class);
Notice that it's using the JBossSecurityContext.class as the logger name.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira