You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by "Jared Bunting (JIRA)" <ji...@apache.org> on 2011/09/19 14:11:08 UTC

[jira] [Assigned] (SHIRO-217) Create JndiObjectFactory to allow JNDI object acquisition during configuration

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

Jared Bunting reassigned SHIRO-217:
-----------------------------------

    Assignee: Jared Bunting

> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira