[WICKET-5262] Lifecycle of CDI object bound to wicket Page

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Invalid
• Affects Version/s: 6.8.0, 6.9.0
• Component/s: wicket-cdi
• Assignee: Igor Vaynberg
• Reporter: Daniel Zwicker
• Created: 02/Jul/13 13:00
• Updated: 02/Jul/13 15:49
• Resolved: 02/Jul/13 15:03

Description

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.

Issue Links

• is related to: WICKET-5261 After deserialize of a page CDI injection should take place