[
https://issues.apache.org/jira/browse/SHIRO-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488609#comment-13488609
]
Mladen Marev edited comment on SHIRO-389 at 11/1/12 11:12 AM:
--------------------------------------------------------------
Actually this is not enough.
If you have this in shiro.ini in OSGi environment:
cacheManager = org.apache.shiro.cache.ehcache.EhCacheManager
securityManager.cacheManager = $cacheManager
shiro does not see the class.
It needs optional import on the exported org.apache.shiro.cache.ehcache
package, so that if it is available as bundle to be able to use it.
Other option is to make shiro-ehcache a fragment to shiro-core.
was (Author: mdmarev):
Actually this is not enough.
If you have this in shiri.ini in OSGi environment:
cacheManager = org.apache.shiro.cache.ehcache.EhCacheManager
securityManager.cacheManager = $cacheManager
shiro does not see the class.
It needs optional import on the exported org.apache.shiro.cache.ehcache
package, so that if it is available as bundle to be able to use it.
Other option is to make shiro-ehcache a fragment to shiro-core.
> 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.1, 1.3.0
> Reporter: Chris Geer
> 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
