Exception using progress bars with Galileio and Jazz 2.0
Hello,
we have a problem using Jazz 2.0 with Galileio. Whenever we open a page with a progress bar, we get an exception, e.g., a plan, the my work page or a work item editor we enhanced. The code for the work item editor is included as well as the exception information. Does somebody have experienced something similar? Thank you very much, Lars section code (Problem is the 4th presentation tag, if left out, all works fine): <section> <presentation> <presentation> <presentation> <presentation> <presentation> </section> Exception for the editor page is: eclipse.buildId=I20090611-1540 java.fullversion=J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr4ifx-20090506_34991 (JIT enabled, AOT enabled) J9VM - 20090506_034991_lHdSMr JIT - r9_20090213_2028 GC - 20090213_AA BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en Framework arguments: -product com.bosch.ubk.idefix.product Command-line arguments: -os win32 -ws win32 -arch x86 -product com.bosch.ubk.idefix.product Error Thu Sep 17 11:39:27 CEST 2009 Unhandled event loop exception org.eclipse.swt.SWTException: Failed to execute runnable (com.ibm.team.apt.internal.common.scripting.ScriptException: com.ibm.team.apt.internal.ui.progress.ProgressLabelProvider: Is not a constructor) at org.eclipse.swt.SWT.error(SWT.java:3884) at org.eclipse.swt.SWT.error(SWT.java:3799) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3855) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3476) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) at org.eclipse.equinox.launcher.Main.main(Main.java:1287) Caused by: com.ibm.team.apt.internal.common.scripting.ScriptException: com.ibm.team.apt.internal.ui.progress.ProgressLabelProvider: Is not a constructor at com.ibm.team.apt.internal.common.scripting.util.JSUtils.createWrappable(JSUtils.java:151) at com.ibm.team.apt.internal.common.scripting.util.Factory$ScriptInvocationHandler$1.run(Factory.java:37) at com.ibm.team.apt.internal.common.scripting.util.Factory$ScriptInvocationHandler$1.run(Factory.java:1) at com.ibm.team.apt.internal.common.scripting.environment.AbstractScriptEnvironment.execute(AbstractScriptEnvironment.java:62) at com.ibm.team.apt.internal.common.scripting.util.Factory$ScriptInvocationHandler.<init>(Factory.java:35) at com.ibm.team.apt.internal.common.scripting.util.Factory$ScriptInvocationHandler.<init>(Factory.java:33) at com.ibm.team.apt.internal.common.scripting.util.Factory.newInstance(Factory.java:82) at com.ibm.team.apt.internal.ide.ui.resource.parts.WorkItemProgressPresentationPart.createContent(WorkItemProgressPresentationPart.java:163) at com.ibm.team.ui.editor.TeamFormSectionPart.createPartContent(TeamFormSectionPart.java:94) at com.ibm.team.ui.editor.TeamFormSectionPart.createPartContents(TeamFormSectionPart.java:84) at com.ibm.team.workitem.ide.ui.internal.editor.WorkItemTeamFormSectionPart.createContent(WorkItemTeamFormSectionPart.java:43) at com.ibm.team.ui.editor.TeamFormSectionPart.init(TeamFormSectionPart.java:57) at com.ibm.team.ui.editor.TeamFormSectionPart.<init>(TeamFormSectionPart.java:45) at com.ibm.team.workitem.ide.ui.internal.editor.WorkItemTeamFormSectionPart.<init>(WorkItemTeamFormSectionPart.java:32) at com.ibm.team.workitem.ide.ui.internal.editor.presentations.WorkItemEditorSections.createSection(WorkItemEditorSections.java:101) at com.ibm.team.workitem.ide.ui.internal.editor.OverviewTab.createFormContent(OverviewTab.java:141) at org.eclipse.ui.forms.editor.FormPage$1.run(FormPage.java:152) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.forms.editor.FormPage.createPartControl(FormPage.java:150) at org.eclipse.ui.forms.editor.FormEditor.pageChange(FormEditor.java:465) at com.ibm.team.ui.editor.TeamFormEditor.pageChange(TeamFormEditor.java:203) at org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:1076) at org.eclipse.ui.forms.editor.FormEditor.setActivePage(FormEditor.java:597) at org.eclipse.ui.forms.editor.SharedHeaderFormEditor.createPages(SharedHeaderFormEditor.java:103) at com.ibm.team.ui.editor.TeamFormEditor.createPages(TeamFormEditor.java:144) at com.ibm.team.workitem.ide.ui.internal.editor.WorkItemEditor.setInput(WorkItemEditor.java:1557) at com.ibm.team.workitem.ide.ui.internal.editor.WorkItemEditor$4.run(WorkItemEditor.java:880) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) ... 23 more |
3 answers
I can reduce the scope of this problem. We used birt framework 2.5.0 SDK and DTP 1.7.0 SDK. With this the problems were there. We switched back to birt 2.3.2 sdk and dtp 1.6.2 sdk. In this case the problem is solved. Also without birt and dtp the problem does not exist.
Cheers, Lars |
And now the presentation tags complete :( |
And now the presentation tags complete :(
<section> <presentation> <presentation> <presentation> <presentation> <presentation> ... </section> |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.