[
https://issues.apache.org/jira/browse/SHIRO-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Les Hazlewood resolved SHIRO-140.
---------------------------------
Resolution: Fixed
Sanity tests committed
> Add a subject-aware ExecutorService implementation to support Subject
> execution on other threads
> ------------------------------------------------------------------------------------------------
>
> Key: SHIRO-140
> URL: https://issues.apache.org/jira/browse/SHIRO-140
> Project: Shiro
> Issue Type: New Feature
> Components: Subject
> Affects Versions: 1.0.0
> Reporter: Les Hazlewood
> Assignee: Les Hazlewood
> Fix For: 1.0.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Currently the Subject.associateWith* methods return objects that are
> associated with the Subject. Then the caller is expected to dispatch the
> callable/runnable to some thread mechanism as they see fit.
> It might be nice to simplify this even further for anyone relying on the
> ExecutorService API, say by creating a SubjectExecutorService implementation
> that:
> 1) Looks up the currently executing Subject
> 2) calls subject.associateWith* methods on the callable/runnable argument
> 3) dispatches the associated callable/runnable to the underlying 'real'
> ExecutorService instance.
> It reduces Shiro-user code complexity in that they don't need to call the
> subject.execute* or subject.associateWith* methods any time they need to
> dispatch to another thread.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
