[ https://issues.apache.org/jira/browse/WICKET-5262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697885#comment-13697885 ]
Daniel Zwicker commented on WICKET-5262: ---------------------------------------- yes, the actual injection is handled by the cdi container. but wicket-cdi calls the BeanManager and not the container. So wicket-cdi must handle the lifecycle of its Components and Behaviors. Not the container. Or have i missed that wicket is now in the JEE spec? > Lifecycle of CDI object bound to wicket Page > -------------------------------------------- > > Key: WICKET-5262 > URL: https://issues.apache.org/jira/browse/WICKET-5262 > Project: Wicket > Issue Type: Bug > Components: wicket-cdi > Affects Versions: 6.8.0, 6.9.0 > Reporter: Daniel Zwicker > Assignee: Igor Vaynberg > > The wicket-cdi module injects object only on > IBehaviorInstantiationListener.onInstantiation and > IComponentInstantiationListener.onInstantiation. After this injection pass > wicket-cdi does not manage the injected objects anymore. It relies on the > normal wicket state management. So the lifecycle of any injected object is > bound to the page (even if this page is serialized and the stored instance is > no longer a cdi object). > I think only the cdi implementation should manage these object. As a > consequence wicket-cdi should inject object before every request is > processed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira