You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@shiro.apache.org by "Kalle Korhonen (JIRA)" <ji...@apache.org> on 2011/08/07 23:42:28 UTC

[jira] [Assigned] (SHIRO-313) Default SessionManager in web environment for Guice support differs from the otherwise.

     [ https://issues.apache.org/jira/browse/SHIRO-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kalle Korhonen reassigned SHIRO-313:
------------------------------------

    Assignee:     (was: Kalle Korhonen)

Not at all. Actually first meant to assign to you but then figured I'll just apply it and in the end, just dropped the ball and didn't do either, sorry.

> Default SessionManager in web environment for Guice support differs from the otherwise.
> ---------------------------------------------------------------------------------------
>
>                 Key: SHIRO-313
>                 URL: https://issues.apache.org/jira/browse/SHIRO-313
>             Project: Shiro
>          Issue Type: Bug
>          Components: Session Management
>    Affects Versions: 1.2.0
>            Reporter: Jared Bunting
>         Attachments: GuiceDefaultSessionManager_SHIRO-313.patch
>
>
> Using Ini setup, or simple construction, the default session manager for a web environment uses servlet container sessions.  It appears that I overlooked this when adding the Guice integration and made the default for a guice web environment native sessions.  Nothing inherently wrong with this other than the glaring inconsistency that I would expect to trip folks up.  I am attaching a patch for this to this ticket.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira