[
https://issues.apache.org/jira/browse/WICKET-3969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195016#comment-13195016
]
John Sarman commented on WICKET-3969:
-------------------------------------
They work great except for the Serialization. I tested it after reading
http://www.adam-bien.com/roller/abien/entry/is_java_ee_6_war So now i have a
UserManager that needs the SessionContext to call
sessionContext.isCallerInRole(role). I set up an Database Realm in Glassfish
and a simple html login page using the j_security_check. After login my wicket
Application starts and using my EJB which is injected via wicket-cdi to my
session object, I am able to implement an IRoleCheckingStrategy that simply
does "return MySession.get().hasAnyRole(roles);" In MySession I inject the
Usermanager and call hasAnyRole, which wraps the sessionContext. So I let the
glassfish handle realm authentication and still benefit from wicket
Authorization. Whether you know it or not your CDI implementation supports EJBs
out of the Box :)
> Add CDI integration
> -------------------
>
> Key: WICKET-3969
> URL: https://issues.apache.org/jira/browse/WICKET-3969
> Project: Wicket
> Issue Type: New Feature
> Reporter: Igor Vaynberg
> Assignee: Igor Vaynberg
> Fix For: 6.0.0
>
>
> Introduce integration with CDI containers which should include
> * injection of components with CDI dependencies
> * conversation scope propagation across pages
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
