Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 356340

Summary: Meeting invitation not sent causes exception
Product: z_Archived Reporter: Alvaro Sanchez-Leon <alvaro.sanchez-leon>
Component: MylynAssignee: Sebastien Dubois <sebastien.dubois>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: lmcbout
Version: unspecified   
Target Milestone: 0.9   
Hardware: All   
OS: All   
Whiteboard:

Description Alvaro Sanchez-Leon CLA 2011-08-31 10:29:28 EDT
The following exception is triggered when a formal review is transitioning from PLANNING TO PREPARATION
and the access to the mailing tool is denied by the user.


!ENTRY org.eclipse.mylyn.reviews.r4e.ui 4 0 2011-08-31 10:23:35.169
!MESSAGE Exception: org.eclipse.core.runtime.CoreException: ComponentObjectModelException: null
!STACK 1
org.eclipse.core.runtime.CoreException: ComponentObjectModelException: null
	at com.ericsson.reviews.r4e.mail.mailVersion.pc.MicrosoftOutlook.createMeetingRequest(MicrosoftOutlook.java:326)
	at org.eclipse.mylyn.reviews.r4e.ui.internal.utils.MailServicesProxy.sendMeetingRequest(MailServicesProxy.java:934)
	at org.eclipse.mylyn.reviews.r4e.ui.internal.utils.MailServicesProxy.sendMeetingRequest(MailServicesProxy.java:904)
	at org.eclipse.mylyn.reviews.r4e.ui.internal.properties.tabbed.ReviewTabPropertySection$1.widgetSelected(ReviewTabPropertySection.java:368)
	at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1062)
	at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:774)
	at org.eclipse.swt.custom.CCombo.listEvent(CCombo.java:1095)
	at org.eclipse.swt.custom.CCombo$1.handleEvent(CCombo.java:115)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
	at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	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:369)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
	at java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1384)
!SUBENTRY 1 com.ericsson.reviews.r4e.mail 4 0 2011-08-31 10:23:35.171
!MESSAGE ComponentObjectModelException: null
Comment 1 Sebastien Dubois CLA 2011-09-01 11:27:23 EDT
The exception is thrown by the outlook connector, so we cannot remove it.  What we can do it do catch it, but do not show it to the user in a dialog.  Anyways if the meeting request is not set properly another dialog will tell the user and the review state will stay at the PLANNING phase
Comment 2 Sebastien Dubois CLA 2011-09-01 11:37:35 EDT
Fix implemented as described above