Community
Participate
Working Groups
BIRT Trace Report does not appear in the Trace Report wizard. Using the TPTP-4.5.0-200712211700 build and the enclosed profile, the BIRT Trace Report does not appear in the Trace Report wizard (see http://help.eclipse.org/help33/topic/org.eclipse.tptp.trace.report.birt.doc.user/tasks/treportmon.xhtml). After debugging, it appears that this report generator (org.eclipse.tptp.trace.report.birt.ui.internal.BIRTTraceReportWizard) is expecting that the selection is a TRCMonitor/TRCNode/TRCProcessProxy/TRCAgentProxy/INavigatorItem, but the actual selection is an org.eclipse.hyades.trace.views.adapter.internal.MemoryStatisticViewer. Both the org.eclipse.tptp.trace.report.birt.ui.internal.BIRTTraceReportWizard.isAvailable(ISelection) and org.eclipse.tptp.trace.report.birt.ui.internal.BIRTTraceReportWizard.export(Object) will need updates. Interesting, there are other report types (org.eclipse.hyades.trace.ui.internal.reports.XMLTraceReportWizard.java and org.eclipse.hyades.trace.ui.internal.reports.CSVTraceReportWizard.java) are subclassed from org.eclipse.hyades.trace.ui.internal.reports.HTMLTraceReportWizard which have the same problem (RCMonitor/TRCNode/TRCProcessProxy/TRCAgentProxy/INavigatorItem versus MemoryStatisticViewer) so they do not appear in the Trace Report wizard. Note: Once 214746 is completed, this defect should change component owners.
Created attachment 86468 [details] Profiler project.
Trace BIRT report was designed and implemented for selection in Profiling Monitor view. Hence, the org.eclipse.tptp.trace.report.birt.ui.internal.BIRTTraceReportWizard.isAvailable(ISelection) method is verifying TRCObject selection from Profiling Monitor view and not Statistics View classes. The XML, HTML and CVS reports work okay in the latest TPTP CVS base.
Closing.