Re: Wicket-Spring 1.4.8 runs into exception in unit test
Did you upgrade to spring 3? I ran into an issue with the testng spring test not creating the application context before wicket tester tried to use it (iirc @BeforeTest executed before the super classes @BeforeClass) Ended up switching anything annotated with @BeforeTest to @BeforeMethod. I assume junit has similar annotations. On Tue, May 4, 2010 at 11:15 PM, Jeremy Thomerson wrote: > Is your unit test setting up the application before it starts (i.e. in the > setUp method if you're using junit?). If you can't figure it out, create a > quickstart that demonstrates it, and attach that to a JIRA. > > -- > Jeremy Thomerson > http://www.wickettraining.com > > > > On Tue, May 4, 2010 at 11:42 AM, Per Newgro wrote: > > > Hi *, > > > > today i updated wicket from 1.4.7 to 1.4.8. I found a hardcoded > dependency > > to wicket-spring 1.4.1 in my pom. > > I updated it to 1.4.8 to. Now i get in my page test the following > exception > > in setup. But what does it mean? Where > > can i change something to make this work. Until now i didn't found a > > starting point. Maybe someone solved this > > already. - Unit test layout is related to world-known wicket-example. > > > > 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.spring.injection.annot.test.AnnotApplicationContextMock.(AnnotApplicationContextMock.java:61) > >at my.chaman.frontend.wicket.MockContext.(MockContext.java:11) > >at > > > my.chaman.frontend.wicket.ApplicationForTesting.(ApplicationForTesting.java:11) > >at > > > my.chaman.frontend.wicket.pricetype.edit.pricetypetext.PriceTypeTextPageTest.setUp(PriceTypeTextPageTest.java:29) > >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > >at > > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > >at > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > >at java.lang.reflect.Method.invoke(Method.java:597) > >at > > > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > >at > > > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > >at > > > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > >at > > > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27) > >at > > > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) > >at > > > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > >at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) > >at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) > >at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) > >at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) > >at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) > >at org.junit.runners.ParentRunner.run(ParentRunner.java:236) > >at > > > org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:46) > >at > > > org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > >at > > > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) > >at > > > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) > >at > > > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) > >at > > > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) > > > > Cheers > > Per > > > > > > - > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > >
Re: Wicket-Spring 1.4.8 runs into exception in unit test
Is your unit test setting up the application before it starts (i.e. in the setUp method if you're using junit?). If you can't figure it out, create a quickstart that demonstrates it, and attach that to a JIRA. -- Jeremy Thomerson http://www.wickettraining.com On Tue, May 4, 2010 at 11:42 AM, Per Newgro wrote: > Hi *, > > today i updated wicket from 1.4.7 to 1.4.8. I found a hardcoded dependency > to wicket-spring 1.4.1 in my pom. > I updated it to 1.4.8 to. Now i get in my page test the following exception > in setup. But what does it mean? Where > can i change something to make this work. Until now i didn't found a > starting point. Maybe someone solved this > already. - Unit test layout is related to world-known wicket-example. > > 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.spring.injection.annot.test.AnnotApplicationContextMock.(AnnotApplicationContextMock.java:61) >at my.chaman.frontend.wicket.MockContext.(MockContext.java:11) >at > my.chaman.frontend.wicket.ApplicationForTesting.(ApplicationForTesting.java:11) >at > my.chaman.frontend.wicket.pricetype.edit.pricetypetext.PriceTypeTextPageTest.setUp(PriceTypeTextPageTest.java:29) >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >at java.lang.reflect.Method.invoke(Method.java:597) >at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) >at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) >at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) >at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27) >at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) >at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) >at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) >at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) >at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) >at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) >at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) >at org.junit.runners.ParentRunner.run(ParentRunner.java:236) >at > org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:46) >at > org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) >at > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) >at > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) >at > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) >at > org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) > > Cheers > Per > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Wicket-Spring 1.4.8 runs into exception in unit test
Hi *, today i updated wicket from 1.4.7 to 1.4.8. I found a hardcoded dependency to wicket-spring 1.4.1 in my pom. I updated it to 1.4.8 to. Now i get in my page test the following exception in setup. But what does it mean? Where can i change something to make this work. Until now i didn't found a starting point. Maybe someone solved this already. - Unit test layout is related to world-known wicket-example. 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.spring.injection.annot.test.AnnotApplicationContextMock.(AnnotApplicationContextMock.java:61) at my.chaman.frontend.wicket.MockContext.(MockContext.java:11) at my.chaman.frontend.wicket.ApplicationForTesting.(ApplicationForTesting.java:11) at my.chaman.frontend.wicket.pricetype.edit.pricetypetext.PriceTypeTextPageTest.setUp(PriceTypeTextPageTest.java:29) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184) at org.junit.runners.ParentRunner.run(ParentRunner.java:236) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:46) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) Cheers Per - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
