[jira] Resolved: (WICKET-2887) Bootstraping wicket with GuiceWebApplicationFactory fails with exception

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

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

Igor Vaynberg resolved WICKET-2887.
-----------------------------------

      Assignee: Igor Vaynberg
    Resolution: Cannot Reproduce

well, i ran the test from the patch and it passed :) so i am assuming everything is good.

springwebapplicationfactory is "worse" because it is deprecated. i dont much see the point of using the ioc container to create the application object. if you are going to go that far then you may as well use the container's filter-forwarding infrastructure and create the entire wicket filter inside the container.

-igor

> Bootstraping wicket with GuiceWebApplicationFactory fails with exception
> ------------------------------------------------------------------------
>
>                 Key: WICKET-2887
>                 URL: https://issues.apache.org/jira/browse/WICKET-2887
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-guice
>    Affects Versions: 1.4.8, 1.4.9
>            Reporter: Zilvinas Kybartas
>            Assignee: Igor Vaynberg
>         Attachments: WICKET-2887-1.4.9.patch
>
>
> There seems to be some sort of chicken-egg problem:
> org.apache.wicket.WicketRuntimeException: There is no application attached to current thread main
> 	at org.apache.wicket.Application.get(Application.java:179) [wicket-1.4.9.jar:1.4.9]
> 	at org.apache.wicket.injection.web.InjectorHolder.setInjector(InjectorHolder.java:88) [wicket-ioc-1.4.9.jar:1.4.9]
> 	at org.apache.wicket.guice.GuiceComponentInjector.<init>(GuiceComponentInjector.java:102) [wicket-guice-1.4.9.jar:1.4.9]
> 	at org.apache.wicket.guice.GuiceWebApplicationFactory.createApplication(GuiceWebApplicationFactory.java:177) [wicket-guice-1.4.9.jar:1.4.9]
> 	at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:701) [wicket-1.4.9.jar:1.4.9]
> After some digging i found that it is actually a regression made by this issue fix - WICKET-2761.
> If I rollback wicket-guice to 1.4.7, everything starts to work just fine.

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