Wicket with Apache Shiro

[Michael Chandler <Mi...@onassignment.com>]

Has anyone on this list had experience integrating Apache Shiro with their Wicket project?  I've had a good deal of luck implementing the basics of Shiro security in my Wicket app, but I'm struggling with their provided caching implementation with EhCache.  The cacheManager is defined as a bean in my Spring applicationContext.xml per the documentation, but I keep getting this message:

Another CacheManager with same name 'cacheManager' already exists in the same VM. Please > provide unique names for each CacheManager in the config or do one of following: 1. Use one of the CacheManager.create() static factory methods to reuse same CacheManager with same name or create one if necessary 2. Shutdown the earlier cacheManager before creating new one with same name. The source of the existing CacheManager is: DefaultConfigurationSource [ ehcache.xml or ehcache-failsafe.xml ]

I suspect this has to do with the way Wicket behaves with my application context in general and I'm unsure what the work around is.  I was wondering if anyone on this list has used Apache Shiro Security with Spring on their Wicket apps.

Mike Chandler
Programmer Analyst
On Assignment, Inc.
t: 818.878.3187
f: 818.878.6582
NYSE: ASGN
www.onassignment.com<http://www.onassignment.com/>
People First.

Re: Wicket with Apache Shiro

[Martin Grigorov <mg...@apache.org>]

Hi,


On Fri, Jul 26, 2013 at 6:23 PM, Michael Chandler <
Michael.Chandler@onassignment.com> wrote:

> Has anyone on this list had experience integrating Apache Shiro with their
> Wicket project?  I've had a good deal of luck implementing the basics of
> Shiro security in my Wicket


I am aware of these two integrations:
-
https://github.com/wicketstuff/core/tree/master/jdk-1.6-parent/shiro-security
-
https://github.com/55minutes/fiftyfive-wicket/tree/master/fiftyfive-wicket-shiro


> app, but I'm struggling with their provided caching implementation with
> EhCache.  The cacheManager is defined as a bean in my Spring
> applicationContext.xml per the documentation, but I keep getting this
> message:
>
> Another CacheManager with same name 'cacheManager' already exists in the
> same VM. Please > provide unique names for each CacheManager in the config
> or do one of following: 1. Use one of the CacheManager.create() static
> factory methods to reuse same CacheManager with same name or create one if
> necessary 2. Shutdown the earlier cacheManager before creating new one with
> same name. The source of the existing CacheManager is:
> DefaultConfigurationSource [ ehcache.xml or ehcache-failsafe.xml ]
>
> I suspect this has to do with the way Wicket behaves with my application
> context in general and I'm unsure what the work around is.  I was wondering
> if anyone on this list has used Apache Shiro Security with Spring on their
> Wicket apps.
>

This question should be asked in Shiro's users@ list, I think.


>
> Mike Chandler
> Programmer Analyst
> On Assignment, Inc.
> t: 818.878.3187
> f: 818.878.6582
> NYSE: ASGN
> www.onassignment.com<http://www.onassignment.com/>
> People First.
>
>