Once I fixed the endless loop I got
wicket.WicketRuntimeException:
javax.management.InstanceAlreadyExistsException:
wicket.app.WicketTester:type=Application,name=ApplicationSettings
at wicket.jmx.Initializer.init(Initializer.java:97)
at wicket.Initializer.init(Initializer.java:51)
at wicket.Application.initialize(Application.java:808)
at wicket.Application.initializeComponents(Application.java:831)
at wicket.Application.initializeComponents(Application.java:577)
at wicket.protocol.http.WicketFilter.init(WicketFilter.java:344)
at
wicket.protocol.http.MockWebApplication.<init>(MockWebApplication.java:148)
at wicket.util.tester.WicketTester.<init>(WicketTester.java:205)
at wicket.WicketTestCase.setUp(WicketTestCase.java:62)
at junit.framework.TestCase.runBare(TestCase.java:125)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:118)
at junit.framework.TestSuite.runTest(TestSuite.java:208)
at junit.framework.TestSuite.run(TestSuite.java:203)
at
org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
Caused by: javax.management.InstanceAlreadyExistsException:
wicket.app.WicketTester:type=Application,name=ApplicationSettings
at
com.sun.jmx.mbeanserver.RepositorySupport.addMBean(RepositorySupport.java:452)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1410)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:936)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:337)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:497)
at wicket.jmx.Initializer.init(Initializer.java:68)
... 21 more
On 10/15/06, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
Did someone recently change the initializer code? It seems like it is
causing endless loops with the junit tests
Juergen
