[
https://issues.apache.org/jira/browse/SHIRO-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17680314#comment-17680314
]
Lenny Primak edited comment on SHIRO-337 at 1/24/23 6:40 PM:
-------------------------------------------------------------
I don't quite understand this:
I can see how you can Inject Subject and SecurityManager with this PR, but I
don't see how Session can be injected. Is the description wrong then (at the
top of this issue?)
Also, I still don't see where this PR makes CDI beans available in shiro.ini,
can you point me in the right direction?
I am trying to understand what this code does (or, more importantly doesn't do),
Thank you!
was (Author: lprimak):
I don't quite understand this:
I can see how you can Inject Subject and SecurityManager with this PR, but I
don't see how that can be injected. Is the description wrong then (at the top
of this issue?)
Also, I still don't see where this PR makes CDI beans available in shiro.ini,
can you point me in the right direction?
I am trying to understand what this code does (or, more importantly doesn't do),
Thank you!
> adding support for CDI
> ----------------------
>
> Key: SHIRO-337
> URL: https://issues.apache.org/jira/browse/SHIRO-337
> Project: Shiro
> Issue Type: New Feature
> Components: Integration: JEE
> Affects Versions: 1.2.0, 1.2.1
> Reporter: Romain Manni-Bucau
> Priority: Major
> Labels: patch, patch-with-test
> Attachments: SHIRO-337-2.patch, SHIRO-337-3.patch, SHIRO-337.patch
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> As there is a spring or guice integration, a CDI integration could be
> welcomed.
> Features:
> * enable shiro components to be injectables (subject, session, security
> manager)
> * enable shiro to be configurable via cdi beans (producer methods) instead
> of shiro.ini
> * make interceptors for Shiro annotations (similar/duplicate of SHIRO-898)
> * Make CDI beans available in shiro.ini
> * Async / "reactive" support
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
