[
https://issues.apache.org/jira/browse/SHIRO-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13543126#comment-13543126
]
Chris Geer commented on SHIRO-389:
----------------------------------
Jared, I tend to agree that a fragment would be a better way to handle it.
On a side note, I'd also argue that in OSGI you don't need the INI
configurations for wiring assuming you are using a non-INI based
username/password store. Using something like Blueprint allows you to wire
together all the components in an OSGI standard way. That's what I'm doing
which is why I didn't have the problem Mladen saw.
As an example:
<bean id="sessionMgr"
class="org.apache.shiro.session.mgt.eis.EnterpriseCacheSessionDAO">
<property name="activeSessionsCacheName"
value="shiro-activeSessionCache"/>
</bean>
<bean id="ehCacheMgr" class="org.apache.shiro.cache.ehcache.EhCacheManager"
destroy-method="destroy">
<property name="cacheManagerConfigFile" value="file:./etc/ehcache.xml"/>
</bean>
<bean id="dbRealm" class="...JdbcRealm">
<property name="authenticationCachingEnabled" value="true"/>
</bean>
<bean id="secMgr" class="org.apache.shiro.mgt.DefaultSecurityManager">
<argument ref="dbRealm"/>
<property name="sessionManager.sessionDAO" ref="sessionMgr"/>
<property
name="subjectDAO.sessionStorageEvaluator.sessionStorageEnabled" value="false"/>
<property name="sessionManager.sessionValidationSchedulerEnabled"
value="false"/>
<property name="cacheManager" ref="ehCacheMgr"/>
</bean>
> 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
