You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2025/01/10 09:02:00 UTC

[jira] [Commented] (WICKET-7125) To use cdi-unit CreationalContext to inject beans in Wicket components during tests

    [ https://issues.apache.org/jira/browse/WICKET-7125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17911854#comment-17911854 ] 

ASF subversion and git services commented on WICKET-7125:
---------------------------------------------------------

Commit 61f4695ae61bb3e5866d4a39771f36492d280d8c in wicket's branch refs/heads/dependabot/maven/metrics.version-4.2.29 from Pedro Henrique Oliveira dos Santos
[ https://gitbox.apache.org/repos/asf?p=wicket.git;h=61f4695ae6 ]

WICKET-7125 setBeanManager method test


> 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
>             Fix For: 10.3.0
>
>
> 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)