shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Les Hazlewood (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SHIRO-217) Create JndiObjectFactory to allow JNDI object acquisition during configuration
Date Thu, 05 Jan 2012 01:02:39 GMT

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

Les Hazlewood resolved SHIRO-217.
---------------------------------

    Resolution: Fixed

Looks good to me!
                
> Create JndiObjectFactory to allow JNDI object acquisition during configuration
> ------------------------------------------------------------------------------
>
>                 Key: SHIRO-217
>                 URL: https://issues.apache.org/jira/browse/SHIRO-217
>             Project: Shiro
>          Issue Type: New Feature
>          Components: Configuration
>            Reporter: Les Hazlewood
>            Assignee: Jared Bunting
>             Fix For: 1.2.0
>
>
> During configuration, it would be nice to acquire objects from JNDI and use the returned
objects as properties on other configured objects (e.g. in INI config).
> There is a JndiRealmFactory that already supports looking up entire Realms from JNDI,
but it is more likely that lower-level objects would be acquired from JNDI instead (e.g. DataSources)
and the Realms would be configured in INI and use those objects.
> This would be pretty easy to support:  there is already a Shiro Factory interface and
an AbstractFactory class.  A new JndiObjectFactory subclass could be created that uses a JndiLocator
to look up and acquire objects.
> The ReflectionBuilder implementation would need to be changed to handle encountering
Factory objects - if an object in configuration specifies a Factory as a property, the builder
needs to call the factory's getInstance method instead of using the Factory directly.  I think
this could be done in the ReflectionBuilder#resolveReference method without touching any other
code.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message