shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Les Hazlewood (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SHIRO-153) INI config - allow [filters] section to define non-filter objects (for DI configuration) as well as reference objects in [main]
Date Sun, 09 May 2010 07:29:03 GMT

     [ https://issues.apache.org/jira/browse/SHIRO-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Les Hazlewood updated SHIRO-153:
--------------------------------

    Comment: was deleted

(was: Redefining this issue after looking over the source code - we don't want our default
filters potentially conflicting in name with user-defined beans in the [main] section, so
keeping a [filters] section still makes sense.

It should be even more powerful however in that any type of object can also be defined in
the [filters] section, for the purpose of DI configuration for filter objects (e.g. someFilter.property1
= $aPojoReference if necessary).

Also, for the same reason, a filter might need to reference a bean defined in [main], so the
following should be possible as well:

[main]
bar = com.foo.Bar

[filters]
bazFilter = com.foo.BazFilter
bazFilter.bar = $bar

But objects in [main] should typically not be able to reference those in the [filters] section.)

> INI config - allow [filters] section to define non-filter objects (for DI configuration)
as well as reference objects in [main]
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SHIRO-153
>                 URL: https://issues.apache.org/jira/browse/SHIRO-153
>             Project: Shiro
>          Issue Type: Improvement
>          Components: Configuration
>    Affects Versions: 1.0.0
>            Reporter: Les Hazlewood
>            Assignee: Les Hazlewood
>             Fix For: 1.0.0
>
>
> The [main] section and the [filters] section are really just a pool of objects, keyed
by name, but the pools can't 'share' objects from one another.  So if you configured something
in [main] that needed to be referenced from a custom filter in [filters], that is not possible
at the moment.  By putting everything in the main 'pool', objects can reference each other
as needed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message