shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SHIRO-389) Fix OSGI Exports for shiro-ehcache
Date Wed, 09 Jan 2013 08:36:13 GMT

    [ https://issues.apache.org/jira/browse/SHIRO-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547769#comment-13547769
] 

Christian Schneider commented on SHIRO-389:
-------------------------------------------

How about exporting shiro extensions/plugins as OSGi services from the bundle that offers
them. Then you could declare the filter statement or just the interface name in the ini and
resolve the service when evaluating the config. This would avoid that shiro core needs to
know about the impl packages.
                
> Fix OSGI Exports for shiro-ehcache
> ----------------------------------
>
>                 Key: SHIRO-389
>                 URL: https://issues.apache.org/jira/browse/SHIRO-389
>             Project: Shiro
>          Issue Type: Bug
>          Components: Caching 
>    Affects Versions: 1.2.0, 1.2.1
>            Reporter: Chris Geer
>            Assignee: Les Hazlewood
>             Fix For: 1.2.2, 1.3.0
>
>         Attachments: SHIRO_389_core.patch, SHIRO-389.patch
>
>
> Currently the osgi-export in the pom file is org.apache.shiro.ehcache which isn't a valid
package. It should be changed to org.apache.shiro.cache.ehcache

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message