Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 340510 - ServiceHandlerExtensionTest has a compile error
Summary: ServiceHandlerExtensionTest has a compile error
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 1.4   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 1.4 M7   Edit
Assignee: Frank Appel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-20 11:18 EDT by Ivan Furnadjiev CLA
Modified: 2011-03-26 03:16 EDT (History)
1 user (show)

See Also:


Attachments
Fix for compile problem (1.88 KB, patch)
2011-03-25 02:45 EDT, Frank Appel CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan Furnadjiev CLA 2011-03-20 11:18:36 EDT
org.eclipse.rap.ui.tests\RAP UI Tests\org\eclipse\rap\ui\tests\ServiceHandlerExtensionTest.java has a compile error. ServiceManager#getCustomHandler does not exists any more.
Comment 1 Frank Appel CLA 2011-03-25 02:45:56 EDT
Created attachment 191885 [details]
Fix for compile problem

This fix solves the compile problem. Unfortunately currently I'm not able to run the UI testsuite to see whether it also performs as expected. If anybody could do a quick check that would help. Otherwise I will spend some time this weekend to get my suite up and running and see if the patch works and if not what have to be done to get it work :-)
Comment 2 Ivan Furnadjiev CLA 2011-03-25 04:01:53 EDT
Hi Frank, just ran the test suite and get this exception in ServiceHandlerExtensionTest:
java.lang.NoClassDefFoundError: org/eclipse/rwt/Fixture
	at org.eclipse.rap.ui.tests.ServiceHandlerExtensionTest.setUp(ServiceHandlerExtensionTest.java:41)
	at junit.framework.TestCase.runBare(TestCase.java:128)
	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:120)
	at junit.framework.TestSuite.runTest(TestSuite.java:230)
	at junit.framework.TestSuite.run(TestSuite.java:225)
	at junit.framework.TestSuite.runTest(TestSuite.java:230)
	at junit.framework.TestSuite.run(TestSuite.java:225)
	at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130)
	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.rap.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:64)
	at org.eclipse.rap.internal.junit.runtime.Application$2.run(Application.java:74)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137)
	at org.eclipse.swt.widgets.Display.runPendingMessages(Display.java:1146)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1133)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2733)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2694)
	at org.eclipse.ui.internal.Workbench.access$5(Workbench.java:2530)
	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:702)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:685)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:157)
	at org.eclipse.rap.interactiondesign.tests.impl.EntryPointImpl.createUI(EntryPointImpl.java:33)
	at org.eclipse.rwt.internal.lifecycle.EntryPointManagerInstance.createUI(EntryPointManagerInstance.java:79)
	at org.eclipse.rwt.internal.lifecycle.EntryPointManager.createUI(EntryPointManager.java:33)
	at org.eclipse.rap.internal.junit.runtime.Application.createAndRunWorkbench(Application.java:44)
	at org.eclipse.rap.internal.junit.runtime.Application.createUI(Application.java:38)
	at org.eclipse.rwt.internal.lifecycle.EntryPointManagerInstance.createUI(EntryPointManagerInstance.java:79)
	at org.eclipse.rwt.internal.lifecycle.EntryPointManager.createUI(EntryPointManager.java:33)
	at org.eclipse.rwt.internal.lifecycle.RWTLifeCycle.createUI(RWTLifeCycle.java:242)
	at org.eclipse.rwt.internal.lifecycle.RWTLifeCycle$UIThreadController.run(RWTLifeCycle.java:111)
	at java.lang.Thread.run(Thread.java:662)
	at org.eclipse.rwt.internal.lifecycle.UIThread.run(UIThread.java:102)
Caused by: java.lang.ClassNotFoundException: org.eclipse.rwt.Fixture
	at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:513)
	at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429)
	at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
	at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
	... 39 more
Comment 3 Frank Appel CLA 2011-03-26 02:32:53 EDT
Hi Ivan. Thanks for running the suite and sorry that it didn't work.

Finally I've got the UI tests running again in my workspace. The ServiceHandlerExtensionTest should compile and run without failure with the latest version that I've commited to CVS head. Note that I've added the fixture fragment to the RAP UI Tests launch configuration. So IMHO we can mark this issue as resolved.
Comment 4 Ivan Furnadjiev CLA 2011-03-26 03:16:07 EDT
Marked as fixed.