[
https://issues.apache.org/jira/browse/WICKET-5262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697790#comment-13697790
]
Daniel Zwicker edited comment on WICKET-5262 at 7/2/13 1:56 PM:
----------------------------------------------------------------
Ok, i have read the JSR-299 which designate to inject "client proxies" to
handle the state of the objects transparently. In the debugger in can see that
the injection points are just the plain objects. No proxies. But i use the
@Dependent scope. So i think this issue can be closed and the real problem is
https://issues.apache.org/jira/browse/WICKET-5261 as we are using transinet
@Dependent scoped beans.
was (Author: shadowdz):
Ok, i have read the JSR-299 which designate to inject "client proxies" to
handle the state of the objects transparently. In the debugger in can see that
the injection points are just the plain objects. No proxies. But i use the
@Dependant scope. So i think this issue can be closed and the real problem is
https://issues.apache.org/jira/browse/WICKET-5261.
> 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
