[
https://issues.apache.org/jira/browse/SHIRO-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681244#comment-17681244
]
Romain Manni-Bucau commented on SHIRO-337:
------------------------------------------
[~lprimak] yes but no?
- `@RequestScoped` = bound to the thread NOT to the request (if you dont use
sync programming you mess up instanced and can even get exceptions)
- there are several cases shiro will be used without a request (thinking to
batches) and I don't think using request controller would be smooth/help
What's the issue with the dynamic proxy? if it helps cdi has a context proxy
factory which can replace it and the handler could be replaced by a cdi
interceptor but it would be equivalent if relying on interfaces (main
functional diff is it will support subclasses).
> 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
> Assignee: Lenny Primak
> 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) - TODO
> * enable shiro to be configurable via cdi beans (producer methods) instead
> of shiro.ini (triage)
> * (superceeded/merged) make interceptors for Shiro annotations
> (similar/duplicate of SHIRO-898)
> * Make CDI beans available in shiro.ini - TODO
> * Async / "reactive" support (triage)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
