.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Changing-default-session-behavior-tp5715141p5715226.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users
gt;>>>> annotations would also work as intended, with clustering and all.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Martin
>>>>>>>>
>>>>>>>>
>>>>>>>>
;> use
>>>>>>> the
>>>>>>> servlet API in the application instead of the shiro-specific calls.
>>>>>>> Ideally
>>>>>>> annotations would also work as intended, with clustering and a
use
>>>>>>> the
>>>>>>> servlet API in the application instead of the shiro-specific calls.
>>>>>>> Ideally
>>>>>>> annotations would also work as intended, with clustering and all.
>&g
t;> annotations would also work as intended, with clustering and all.
>>>>>>
>>>>>> Regards,
>>>>>> Martin
>>>>>>
>>>>>>
>>>>>> Alex Kotchnev-2 wrote
>>>>>>>
>>>&g
t;>>>> @SessionState.
>>>>>> Both Shiro's subject.getSession() and the @Persist annotation store
>>>>> their
>>>>>> values in the same h
tation store
> >>> their
> >>>> values in the same http session. Is that not working for you ?
> >>>>
> >>>> Cheers,
> >>>>
> >>>> Alex K
> >>>>
> >>>> On Wed, Aug 8, 2012 at 7:20 AM, kata
gt; Alex K
>>>>
>>>> On Wed, Aug 8, 2012 at 7:20 AM, kata <januszkiewicz.marcin@>
>>> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> I am currently using shiro and the tapestry-security plugin to manage
>&
It seems that you could override the session persistence strategy and
replace the usage of http session with Shiro's session -e.g. the
implementation seems to be pretty straightforward e.g. inside of Tapestry ,
look at SessionApplicationStatePersistenceStrategy (
http://www.koders.com/java/fidD25B0
y
>> >> SecurityUtils.getSubject().getSession(). However, this means that the
>> >> application is peppered with fragments of shiro-specific code. Since
>> >> shiro
>> >> uses the servlet session API, is there a way to do this in a way that
>> is
>
So you are using native Shiro session management. Tapestry / Servlet API don't
support that.
If you use a 'real' JEE server like Glassfish, web sessions are clustered /
cached properly for you,
without Shiro native sessions or customDAO etc.
You cannot use Shiro native session management and ex
gt;> Cheers,
>>>>>
>>>>> Alex K
>>>>>
>>>>> On Wed, Aug 8, 2012 at 7:20 AM, kata <januszkiewicz.marcin@>
>>>>> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>&g
t;>>>> I am currently using shiro and the tapestry-security plugin to manage
>>>>> sessions and persist data. Everything works fine when getting the
>>>>> session
>>>>> by
>>>>> SecurityUtils.getSubject().ge
>>> sessions and persist data. Everything works fine when getting the
>>>> session
>>>> by
>>>> SecurityUtils.getSubject().getSession(). However, this means that the
>>>> application is peppered with fragments of shiro-specific code. Since
>&
application is peppered with fragments of shiro-specific code. Since
> >> shiro
> >> uses the servlet session API, is there a way to do this in a way that is
> >> transparent to the application, and hopefully still allow me to use
> >> annotations like @Persist and @SessionState?
> >>
On Wed, Aug 8, 2012 at 4:20 AM, kata wrote:
> I am currently using shiro and the tapestry-security plugin to manage
> sessions and persist data. Everything works fine when getting the session by
> SecurityUtils.getSubject().getSession(). However, this means that the
> application is peppered with
is
>>> transparent to the application, and hopefully still allow me to use
>>> annotations like @Persist and @SessionState?
>>>
>>> Thanks,
>>> Martin
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>
ons like @Persist and @SessionState?
>>
>> Thanks,
>> Martin
>>
>>
>>
>> --
>> View this message in context:
>> http://tapestry.1045711.n5.nabble.com/Changing-default-session-behavior-tp5715141.html
>> Sent from the Tapestry - User mailing list
message in context:
> http://tapestry.1045711.n5.nabble.com/Changing-default-session-behavior-tp5715141.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-
shiro
uses the servlet session API, is there a way to do this in a way that is
transparent to the application, and hopefully still allow me to use
annotations like @Persist and @SessionState?
Thanks,
Martin
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Changing-default
20 matches
Mail list logo
