You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by "Francois Papon (Jira)" <ji...@apache.org> on 2020/04/13 10:54:00 UTC
[jira] [Updated] (SHIRO-617) ShiroFilter initialize WebEnvironment
on startup
[ https://issues.apache.org/jira/browse/SHIRO-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francois Papon updated SHIRO-617:
---------------------------------
Fix Version/s: (was: 1.5.3)
2.0.0
> 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
> Assignee: Francois Papon
> Priority: Minor
> Fix For: 2.0.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)