[SHIRO-85] ShiroFilter entries being processed in arbitrary order

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.0.0
• Fix Version/s: 0.9
• Component/s: Configuration
• Assignee: Les Hazlewood
• Reporter: Andy Tripp
• Created: 20/Aug/09 18:35
• Updated: 11/Jun/10 22:00
• Resolved: 20/Aug/09 18:43

Description

Copied over from the Ki issue. Original text:

Entries in a ShiroFilter configuration are not being processed in the order they are listed in.
If we have these lines:
sessionManager=org.apache.shiro.web.session.DefaultWebSessionManager
securityManager.sessionManager = $sessionManager
securityManager.sessionDAO = $sessionDAO
...and line 3 is processed before line 2, the setSessionManager() call for the first line fails because the sessionManager is a ServletContainerSessionManager rather than a DefaultWebSessionManager.

In ReflectionBuilder.buildObjects(), instanceMap and propertyMap need
to be LinkedHashMap type, not just HashMap. With HashMap, the
properties in ShiroFilter are being processed in arbitrary order,
rather than the order listed.

See the "need more help with SSO" thread in the Shiro mailing list:
http://mail-archives.apache.org/mod_mbox/incubator-shiro-user/200908.mbox/browser