[
https://issues.apache.org/jira/browse/WICKET-7125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17891608#comment-17891608
]
Pedro Henrique Oliveira dos Santos edited comment on WICKET-7125 at 10/21/24
5:16 PM:
--------------------------------------------------------------------------------------
Hi devs,
using the new cdi-unit dependency, I could only make it work in the wicket-cdi
tests by stop making the project a Java Platform Module (removing the
module-info.java file). Does someone already had this issue? If not, are you ok
with moving wicket-cdi tests to a new project (wicket-cdi-tests, it would fix
the problem)?
was (Author: pedro):
Hi devs,
using the new cdi-unit dependency, I could only make it work in the wicket-cdi
tests by stop making the poject a Java Platform Module (removing the
module-info.java file). Does someone already had this issue? If not, are you ok
with moving wicket-cdi tests to a new poject (wicket-cdi-tests, it would fix
the problem)?
> 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
> 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)
