shiro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jared Bunting (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SHIRO-313) Default SessionManager in web environment for Guice support differs from the otherwise.
Date Wed, 04 Jan 2012 03:38:39 GMT

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

Jared Bunting resolved SHIRO-313.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2.0

Definitely complete - had been waiting on my access to resolve and then it fell by the wayside
once I got that access.
                
> 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
>            Assignee: Jared Bunting
>             Fix For: 1.2.0
>
>         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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message