[
https://issues.apache.org/jira/browse/SHIRO-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681696#comment-17681696
]
Romain Manni-Bucau commented on SHIRO-337:
------------------------------------------
[~lprimak] jsf deps for ex makes it undesired in web profile (more work -
excludes+conflicts - and maintainance for consumers - cve for ex). It is not
strictly broken but WP apps are either jsf or jaxrs since its creation so libs
must stick to it and not lead to x2 work for consumers. Also some classes can
make scanning behaving weird due to the ee assumptions.
> 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: 3h
> 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) - Done
> * (superceeded/merged) make interceptors for Shiro annotations
> (similar/duplicate of SHIRO-898)
> * Make CDI beans available in shiro.ini - Done
> * enable shiro to be configurable via cdi beans (producer methods) instead
> of shiro.ini (needs triage examples)
> * 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]
