shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Les Hazlewood (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (SHIRO-197) Ini and Ini.Section should retain key-value definition order
Date Thu, 09 Dec 2010 18:28:00 GMT

     [ https://issues.apache.org/jira/browse/SHIRO-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Les Hazlewood resolved SHIRO-197.
---------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 1.0.1)
                   1.1.0

This was resolved in Shiro 1.1

> Ini and Ini.Section should retain key-value definition order
> ------------------------------------------------------------
>
>                 Key: SHIRO-197
>                 URL: https://issues.apache.org/jira/browse/SHIRO-197
>             Project: Shiro
>          Issue Type: Bug
>          Components: Configuration
>    Affects Versions: 1.0.0
>            Reporter: Les Hazlewood
>            Assignee: Les Hazlewood
>            Priority: Critical
>             Fix For: 1.1.0
>
>         Attachments: SHIRO-197.patch
>
>
> Currently the Ini class and it's nested Section class use java.util.Properties for parsing
section content.  The Properties class does not retain definition order.  This logic should
be refactored to use a LinkedHashMap<String,String> instead to guarantee correct ordering
in any INI [urls] sections.
> Note that fixing this issue should fix SHIRO-184.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message