You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by "Kalle Korhonen (JIRA)" <ji...@apache.org> on 2009/02/22 08:09:01 UTC

[jira] Created: (JSEC-61) PathConfigProcessor.processPathConfig() should return Filter

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
            Priority: Trivial
             Fix For: 1.0


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.


[jira] Resolved: (JSEC-61) PathConfigProcessor.processPathConfig() should return Filter

Posted by "Jeremy Haile (JIRA)" <ji...@apache.org>.
     [ 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.


[jira] Updated: (JSEC-61) PathConfigProcessor.processPathConfig() should return Filter

Posted by "Kalle Korhonen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JSEC-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kalle Korhonen updated JSEC-61:
-------------------------------

    Attachment: JSEC-61.patch

Change signature of PathMatchingFilter.processPathConfig to return Filter. 

> 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
>            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.


[jira] Moved: (KI-53) PathConfigProcessor.processPathConfig() should return Filter

Posted by "Alan Cabrera (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KI-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alan Cabrera moved JSEC-61 to KI-53:
------------------------------------

        Fix Version/s:     (was: 1.0)
          Component/s:     (was: Web)
    Affects Version/s:     (was: 0.9)
                  Key: KI-53  (was: JSEC-61)
              Project: Ki  (was: JSecurity)

> PathConfigProcessor.processPathConfig() should return Filter
> ------------------------------------------------------------
>
>                 Key: KI-53
>                 URL: https://issues.apache.org/jira/browse/KI-53
>             Project: Ki
>          Issue Type: Improvement
>            Reporter: Kalle Korhonen
>            Assignee: Jeremy Haile
>            Priority: Trivial
>         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.