[jira] Resolved: (WICKET-3099) initParameters not available when testing via WicketTester

["Igor Vaynberg (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-3099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Igor Vaynberg resolved WICKET-3099.
-----------------------------------

    Resolution: Won't Fix
      Assignee: Igor Vaynberg

test environments do not support parsing your web.xml. read the parameter inside some method in your application subclass, and override it during the test to return whatever value you want.

> initParameters not available when testing via WicketTester
> ----------------------------------------------------------
>
>                 Key: WICKET-3099
>                 URL: https://issues.apache.org/jira/browse/WICKET-3099
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4.12
>            Reporter: Eric Le Lay
>            Assignee: Igor Vaynberg
>            Priority: Minor
>         Attachments: filterconfig.zip
>
>
> Please see the attached simple application.
> It reads an init-param in web.xml and displays its value in HomePage.
> It runs fine (mvn jetty:run) but HomePageTest fails.
> I traced it down to org.apache.wicket.protocol.http.MockWebApplication(final WebApplication application, final String path),
> where a dummy FilterConfig is created, which always returns null in getInitParameter().
> How can I set init parameters during tests ?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.