[
https://issues.apache.org/jira/browse/WICKET-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marek Zganiacz updated WICKET-3358:
-----------------------------------
Component/s: wicket-guice
> Wicket-Guice integration fails - can't find application attached to current
> thread
> ----------------------------------------------------------------------------------
>
> Key: WICKET-3358
> URL: https://issues.apache.org/jira/browse/WICKET-3358
> Project: Wicket
> Issue Type: Bug
> Components: wicket-guice
> Affects Versions: 1.4.8
> Environment: Windows 7, JSDK 1.6.21, Maven 3.0.3
> Reporter: Marek Zganiacz
>
> Simply by starting new project from wicket archetype, then adding a
> dependency to guice 2.0 and wicket-guice 1.4.8 and providing the guice module
> through web.xml to GuiceComponentInjector one can get the exception when
> starting jetty:
> org.apache.wicket.WicketRuntimeException: There is no application attached to
> current thread main
> at org.apache.wicket.Application.get(Application.java:179)
> at
> org.apache.wicket.injection.web.InjectorHolder.setInjector(InjectorHolder.java:88)
> at
> org.apache.wicket.guice.GuiceComponentInjector.<init>(GuiceComponentInjector.java:102)
> at
> org.apache.wicket.guice.GuiceWebApplicationFactory.createApplication(GuiceWebApplicationFactory.java:177)
> at
> org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:701)
> at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:713)
> ...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
