[
https://issues.apache.org/jira/browse/SHIRO-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15941169#comment-15941169
]
Marco Descher commented on SHIRO-617:
-------------------------------------
I am working on such a pull request. A question aside, I currently have to use
the IniShiroFilter due to this.bug but also it seems, that I have to use it for
another reason - I cannot specify a configPath on a ShiroFilter but only an
IniShiroFilter. Is this true? Does this qualify for another bug report?
> ShiroFilter initialize WebEnvironment on startup
> ------------------------------------------------
>
> Key: SHIRO-617
> URL: https://issues.apache.org/jira/browse/SHIRO-617
> Project: Shiro
> Issue Type: Improvement
> Reporter: Marco Descher
> Priority: Minor
>
> Following up to
> http://shiro-developer.582600.n2.nabble.com/Deprecation-of-org-apache-shiro-web-servlet-IniShiroFilter-td7205283.html
> I am integrating shiro into our OSGI based product. The requirement to
> register the WebEnvironment listener on startup is a real problem.
> ""it would be extremely easy to create a subclass of ShiroFilter that
> initializes the necessary WebEnvironment at filter startup. If you
> can't use a servlet context listener, this would be the next best
> thing and would work as expected. The EnvironmentLoaderListener is
> extremely minimal on purpose - the real work is done in the parent
> class, which can be used from a Filter easily. ""
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
