[
https://issues.apache.org/jira/browse/SHIRO-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kalle Korhonen resolved SHIRO-110.
----------------------------------
Resolution: Fixed
Removed SubjectBinder and resolving with comments:
"Finally there is a way to have the Subject.Binder indicate this
session binding is desired any time a Subject is constructed. We
could have something like Subject.Binder().bindToSession(true);. That
call would translate into a flag that is set in the subject context
map sent to the SubjectFactory. The SubjectFactory implementation
would return a DelegatingSubject instance that could execute the
bind-to-session-after-login logic based on that flag (i.e. that logic
wouldn't be in the SecurityManager implementation - it'd be in the
Subject implementation). If we decide this is a good idea, it is
definitely possible.
- Les"
see:
http://mail-archives.apache.org/mod_mbox/incubator-shiro-dev/201002.mbox/%[email protected]%3e
> Remove org.apache.shiro.mgt.SubjectBinder and its usages
> --------------------------------------------------------
>
> Key: SHIRO-110
> URL: https://issues.apache.org/jira/browse/SHIRO-110
> Project: Shiro
> Issue Type: Improvement
> Components: Subject
> Reporter: Les Hazlewood
> Assignee: Kalle Korhonen
> Fix For: 1.0.0
>
>
> This was introduced in 1.0 development and can be easily removed before 1.0
> final - it is not referenced in the public-facing API and is used for
> implementation support only. This needs to be done as the SecurityManager
> will no longer need to maintain thread state (making it 100% stateless) since
> Subject.Builder or its end-users would be responsible for that.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
