[
https://issues.apache.org/jira/browse/SHIRO-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13549023#comment-13549023
]
Achim Nierbeck commented on SHIRO-389:
--------------------------------------
I have to second Christian on this.
The proper solution for this would be what's called the White-Board-Pattern.
Shiro needs to provide an interface for "Cache Managers", and opens a Service
Tracker listening for this interface.
Now anybody is able to add additional Cache Mangers by implementing this
interface and registering it as a service.
Shiro will pick those up and will be able to use them, since they all use the
interface the core bundle doesn't need to know of any other optional packages.
If this kind of solution isn't possible, you have to fallback to the fragment
solution. It's the cleanest solution at hand for this kind of issue.
> 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
