java.lang.IllegalArgumentException

Invalid configuration type: '${wicket.MODE}'. Must be "development" or "deployment".

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web16590

  • Invalid configuration type: '$ {wicket.MODE} '. Must be "development" or "deployment".
  • via Apache's JIRA Issue Tracker by Gilberto C Andrade, 9 months ago
    Invalid configuration type: '${wicket.MODE}'. Must be "development" or "deployment".
  • via dezyre.com by Unknown author, 1 year ago
    configuration must be a '.properties' or a '.xml' file
  • Stack trace

    • java.lang.IllegalArgumentException: Invalid configuration type: '${wicket.MODE}'. Must be "development" or "deployment". at org.apache.wicket.protocol.http.WebApplication.getConfigurationType(WebApplication.java:667) at org.apache.wicket.Application.configure(Application.java:297) at org.apache.wicket.protocol.http.WebApplication.internalInit(WebApplication.java:610) at org.apache.wicket.Application.initApplication(Application.java:804) at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:346) at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:286) at org.apache.catalina.core.ApplicationFilterConfig.initFilter(ApplicationFilterConfig.java:281) at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:262) at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:107) at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4656) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5312) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559) at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.