You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Eric Le Lay (JIRA)" <ji...@apache.org> on 2010/10/07 15:29:31 UTC

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

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

Eric Le Lay updated WICKET-3099:
--------------------------------

    Attachment: filterconfig.zip

quick-start demonstrating the issue

> 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
>         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.