Dear Devs and users, a few day ago a discussion in Slack came up about shiro.ini. It is the number one feature Shiro is known for, and it's certainly not going away. However, it draws in a few extra dependencies (beanutils, collections 3, etc).
OTOH, we don't really provide a convenient way to use other configuration formats out of the box: Java based configuration (using stages builders), maybe TOML and/or YAML or even XML (which has schema!) So, we'd like to know what you think about something like this: Maybe make shiro.ini support an extra dependency in Shiro 3 and an optional dependency in Shiro 4, and also support other configuration formats more conveniently. Since this is extra work for us as maintainers, it'll only be useful if this is actually requested by you (the users/community). The docs already need to be updated, there's not a lot information regarding the web servlet (there's an undocumented parameter, shiroClass or so). That said, it's already possible, but not conveniently doable nor documented. So, please let us know how you think about this - more ideas are welcome! - Ben
