| Summary: | Enhance the support for events received on the same stream that needs to be loaded in multiple domains/contexts | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Paul Slauenwhite <paulslau> |
| Component: | TPTP | Assignee: | Marius Slavescu <slavescu> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | ashishkumarmathur, eejessee, jptoomey, kdsiefke, sluiman |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | housecleaned460 | ||
| Bug Depends on: | |||
| Bug Blocks: | 145146, 148236 | ||
|
Description
Paul Slauenwhite
This should work as I explained in yesterday call regarding this subject (at least when loading Common Base Events/Trace/Statistical events from a test execution result stream or an Common Base Events/Trace/Statistical stream). If a specific context is required in a loader then that loader has to provide one if no context was set upfront when the XMLLoader was initialized. Althogh most of the loaders do this, there are some loaders that don't follow this rule, each domain model owner will need to add this logic to those loaders. We also need to investigate how we could link in a generic way the data that comes from same stream and goes in different models/resources (initially a resource level link at least, that can be used to limit the scope of a correlation by time operation). This will cover also bug 139557. As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As such, TPTP is not delivering enhancements. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement is resolved as WONTFIX. For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html). As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As such, TPTP is not delivering enhancements. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement is resolved as WONTFIX. For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html). Closing. |