[
https://issues.apache.org/jira/browse/WICKET-7125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17892091#comment-17892091
]
Andrea Del Bene commented on WICKET-7125:
-----------------------------------------
Hi,
I'm not used to work with cdi-unit but I guess the problem is the same we had
with wicket-core and we actually solved it introducing a separated test module
like you suggest. However I m not sure if this could be introduced amid a
version life cycle (i.e. version 10.3.0) or it must be targeted for the next
main release 11.
> To use cdi-unit CreationalContext to inject beans in Wicket components during
> tests
> -----------------------------------------------------------------------------------
>
> Key: WICKET-7125
> URL: https://issues.apache.org/jira/browse/WICKET-7125
> Project: Wicket
> Issue Type: Bug
> Components: wicket-cdi
> Affects Versions: 10.2.0
> Reporter: Pedro Henrique Oliveira dos Santos
> Assignee: Pedro Santos
> Priority: Major
>
> Currently, wicket-cdi doesn't offer the user an opportunity to set a custom
> BeanManager in the BeanManagerLookup.
> During tests, it is important to have such API so the user could set the
> BeanManager created by cdi-unit with its own test environment configurations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
