[weld-issues] [JBoss JIRA] (WELD-885) NPE in org.jboss.weld.wicket.util.NonContextual.<init>

[Ondrej Zizka (Issue Comment Edited) (JIRA)]

    [ https://issues.jboss.org/browse/WELD-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642553#comment-12642553 ] 

Ondrej Zizka edited comment on WELD-885 at 11/14/11 10:09 AM:
--------------------------------------------------------------

Yes they are. I guess I filed this issue before I knew there was a separate seam-wicket jira repo.

I can't move it there though.
                
      was (Author: ozizka):
    Yes they are. I guess I filed this issue before I knew there was a separate seam-wicket jira module.
                  
> NPE in org.jboss.weld.wicket.util.NonContextual.<init>
> ------------------------------------------------------
>
>                 Key: WELD-885
>                 URL: https://issues.jboss.org/browse/WELD-885
>             Project: Weld
>          Issue Type: Bug
>          Components: Servlet Container Support
>    Affects Versions: 1.0.1.Final
>         Environment: Jetty 6.1.26
> Wicket 1.4.16
>            Reporter: Ondrej Zizka
>
> I have a standalone app with embedded Jetty running a Wicket app.
> I added weld-wicket as dependency, and after I changed parent class
> of my WicketApplication to WeldApplication and tried to run, the NPE occured.
> Whole project can be seen at 
> http://ondrazizka.googlecode.com/svn/trunk/bots/JawaBot/branches/2.0  r147
> 20:56:17.343 ERROR [main] /  unavailable
> java.lang.NullPointerException
> 	at org.jboss.weld.wicket.util.NonContextual.<init>(NonContextual.java:33)
> 	at org.jboss.weld.wicket.WeldApplication.internalInit(WeldApplication.java:50)
> 	at org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:723)
> 	at org.apache.wicket.protocol.http.ReloadingWicketFilter.init(ReloadingWicketFilter.java:175)
> 	at org.apache.wicket.protocol.http.WicketServlet.init(WicketServlet.java:219)
> 	at javax.servlet.GenericServlet.init(GenericServlet.java:241)
> 	at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:440)
> 	at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:263)
> 	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> 	at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:736)
> 	at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
> 	at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:518)
> 	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> 	at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
> 	at org.mortbay.jetty.Server.doStart(Server.java:224)
> 	at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> 	at org.jboss.jawabot.web.RunInJetty.run(RunInJetty.java:145)
> 	at org.jboss.jawabot.mod.web.WebModuleHook.initModule(WebModuleHook.java:18)
> 	at org.jboss.jawabot.JawaBotApp.initAndStartModules(JawaBotApp.java:106)
> 	at org.jboss.jawabot.JawaBotApp.main(JawaBotApp.java:53)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira