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

Bug 74857

Summary:	(Plat)Restructure filtering design in launch configuration to properly manage Hyades/RAC Filters from other profiling type filters (e.g., probe filters)
Product:	z_Archived	Reporter:	Wayne Ho <who>
Component:	TPTP	Assignee:	amehrega
Status:	CLOSED FIXED	QA Contact:
Severity:	enhancement
Priority:	P2	CC:	cheryladams, gweidner, mani, martin.boag
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	closed460
Bug Depends on:	90754
Bug Blocks:

Description Wayne Ho

2004-09-23 16:44:21 EDT

The current UI for filtering within the Edit Profiling Set dialogs (under the
Profiling tab of the Launch Configuration Dialog) does not manage filtering very
well.

The Edit Profiling Set provides a set of general filters (shown on the 2nd page
of the wizard) for "generic" filters used by the Data Collection Engine (aka
RAC).  However, other Profiling Types (e.g., some probes) may have their own
specific filters.  It is possible that the user may set filters for the probe,
click on "Next>" and see "generic" filters.  This can be confusing.

Comment 1 Valentina Popescu

2004-11-16 14:57:54 EST

Moving feature to 3.3

Comment 2 Valentina Popescu

2004-11-19 20:10:47 EST

The defect should be discussed in the Hyades commiters meeting before moving to 
a higher release
Moving back to 3.2 i2

Comment 3 Valentina Popescu

2004-11-22 14:43:14 EST

Defect discussed in Hyades committers call and approved to move to a higher 
release

Comment 4 Valentina Popescu

2004-12-13 20:40:04 EST

*** Bug 80515 has been marked as a duplicate of this bug. ***

Comment 5 Valentina Popescu

2004-12-13 20:41:31 EST

While reviewing the profiling filters, this issue needs to be addressed :

New filter sets or changes to the existing filter sets are shared by all 
existing configurations.
It needs to be decided weather selection changes in the filter sets should 
affect existing or new configurations ( I would expect that the filter 
selection should be preserved within the same profiling filter sets ).

Comment 6 Eugene Chan

2005-05-31 11:56:22 EDT

*** Bug 93331 has been marked as a duplicate of this bug. ***

Comment 7 Eugene Chan

2005-05-31 12:04:09 EDT

A potential bug to be consider in restructing the framework. There is request
from downstream product to get notified on selection/event changes made in every
page of edit profiling set wizard. As a result, configuration update is applied
in every page change to make sure changes is preserved on other page to consume.
This create problem when user exit/cancel wizard or launch configration that
update is applied and not be able to roll back.

Comment 8 Ruth Lee

2005-07-12 10:58:15 EDT

Deferring from 4.1 as per the official 4.1 enhancement plan.
http://eclipse.org/tptp/home/project_info/featureplans/features.php?source=All&project=All&release=4.1&file=TPTPFeatures_4.1.xml

Comment 9 amehrega

2006-01-25 15:12:30 EST

Setting the target to future since it has not officially been planned, but this feature is being considered as part of the launch configuration refactoring for JVMTI.

Comment 10 amehrega

2006-03-31 18:44:07 EST

Filters/options can now be applied at the data collector or analysis type level.  This work was done as part of 93212

Comment 11 Paul Slauenwhite

2009-06-30 08:19:23 EDT

As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.