You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Marcin Januszkiewicz <ja...@gmail.com> on 2012/08/02 22:47:03 UTC
tapestry-security with caching
Hi all,
I'm using the latest versions of tapestry and tapestry-security (5.4.3
and 0.4.6 respectively) for basic security and session management.
I wanted to explore other capabilities of the shiro framework like
caching and clustering. My problem with this is that in the
documentation
shiro relies on INI files and the tapestry-security plugin drop
support for INI-configuration since version 0.4.0.
What are my options? Is there a way to load an INI as a resource or
configure the plugin from within tapestry? This post seemed somewhat
relevant:
http://mail-archives.apache.org/mod_mbox/tapestry-users/201103.mbox/%3CAANLkTimVy8dbnzdtvr3eBWt3q2Wer4k_S4TbktK=KiYY@mail.gmail.com%3E
however, it seems less than ideal.
Maybe using tapestry-security is the wrong way of doing this?
--
Regards,
Marcin Januszkiewicz
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: tapestry-security with caching
Posted by Kalle Korhonen <ka...@gmail.com>.
On Thu, Aug 2, 2012 at 1:47 PM, Marcin Januszkiewicz
<ja...@gmail.com> wrote:
> I'm using the latest versions of tapestry and tapestry-security (5.4.3
> and 0.4.6 respectively) for basic security and session management.
> I wanted to explore other capabilities of the shiro framework like
> caching and clustering. My problem with this is that in the
> documentation
> shiro relies on INI files and the tapestry-security plugin drop
> support for INI-configuration since version 0.4.0.
> What are my options? Is there a way to load an INI as a resource or
> configure the plugin from within tapestry? This post seemed somewhat
> relevant:
> http://mail-archives.apache.org/mod_mbox/tapestry-users/201103.mbox/%3CAANLkTimVy8dbnzdtvr3eBWt3q2Wer4k_S4TbktK=KiYY@mail.gmail.com%3E
> however, it seems less than ideal.
> Maybe using tapestry-security is the wrong way of doing this?
Ini files is no panacea. You have the full power of Shiro's API at
your disposal. The ini-file support just calls the setters that you
can do so with type-safe code. You can certainly use caching and
clustering with Shiro.
Kalle
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org