You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by "Jeremy Haile (JIRA)" <ji...@apache.org> on 2009/03/02 04:27:15 UTC
[jira] Resolved: (JSEC-61) PathConfigProcessor.processPathConfig()
should return Filter
[ https://issues.apache.org/jira/browse/JSEC-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Haile resolved JSEC-61.
------------------------------
Resolution: Fixed
Assignee: Jeremy Haile
Kalle - applied change as you suggested.
> PathConfigProcessor.processPathConfig() should return Filter
> ------------------------------------------------------------
>
> Key: JSEC-61
> URL: https://issues.apache.org/jira/browse/JSEC-61
> Project: JSecurity
> Issue Type: Improvement
> Components: Web
> Affects Versions: 0.9
> Reporter: Kalle Korhonen
> Assignee: Jeremy Haile
> Priority: Trivial
> Fix For: 1.0
>
> Attachments: JSEC-61.patch
>
>
> Currently return type of PathConfigProcessor.processPathConfig() is void. Would be nice if it returned a Filter instead to make configuring jsecurity in all-java easier, so you could for example write filters.add(pathMatchingFilter.processPathConfig(path, filterConfig)). It would also open up other interesting possibilities for filter implementations (delegating proxy filters etc.). The change is fully backwards compatible and simple, see patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.