I'm thinking that the best way to "Fix" this is to remove the
following two lines:
//convenient alias:
defaults.put("sm", securityManager);
Any objections?
Regards,
Alan
On Nov 23, 2008, at 3:43 PM, Alan Cabrera (JIRA) wrote:
[ https://issues.apache.org/jira/browse/JSEC-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Cabrera updated JSEC-30:
-----------------------------
Description: Aliases in the ini configuration builder do not work
correctly. When one gets updated the aliases do not. This can
cause problems if one is explicitly creating a security manager and
it gets overwritten by the default created and added w/ the "alias"
sm. In this case the default replaces the explicitly created
security manager. (was: Aliases in the ini configuration builder do
not work correctly. When If one gets updated the aliases do not.)
Aliases in the ini configuration builder do not work correctly
--------------------------------------------------------------
Key: JSEC-30
URL: https://issues.apache.org/jira/browse/JSEC-30
Project: JSecurity
Issue Type: Bug
Components: Configuration
Affects Versions: 0.9
Reporter: Alan Cabrera
Fix For: 1.0
Aliases in the ini configuration builder do not work correctly.
When one gets updated the aliases do not. This can cause problems
if one is explicitly creating a security manager and it gets
overwritten by the default created and added w/ the "alias" sm. In
this case the default replaces the explicitly created security
manager.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
