Download
Getting Started
Members
Projects
Community
Marketplace
Events
Planet Eclipse
Newsletter
Videos
Participate
Report a Bug
Forums
Mailing Lists
Wiki
IRC
How to Contribute
Working Groups
Automotive
Internet of Things
LocationTech
Long-Term Support
PolarSys
Science
OpenMDM
More
Community
Marketplace
Events
Planet Eclipse
Newsletter
Videos
Participate
Report a Bug
Forums
Mailing Lists
Wiki
IRC
How to Contribute
Working Groups
Automotive
Internet of Things
LocationTech
Long-Term Support
PolarSys
Science
OpenMDM
Toggle navigation
Bugzilla – Attachment 58034 Details for
Bug 156527
Provide extension point to extend Export Log Set dialog
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Requests
|
Help
|
Log In
[x]
|
Terms of Use
|
Copyright Agent
Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read
this important communication.
Updated feature document
hf_156527.htm (text/html), 5.80 KB, created by
Alex Nan
on 2007-02-01 12:23:08 EST
(
hide
)
Description:
Updated feature document
Filename:
MIME Type:
Creator:
Alex Nan
Created:
2007-02-01 12:23:08 EST
Size:
5.80 KB
patch
obsolete
><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> ><html> ><head> ><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> ><title>TPTP feature 156527</title> ><link rel="stylesheet" type="text/css" href="http://eclipse.org/default_style.css"> ></head> ><body> ><h1>TPTP feature: 156527</h1> ><table border="0" cellpadding="2" cellspacing="2"> > <tbody> > <tr> > <td width="100">Author:</td> > <td>Eugene Chan <br/> > Alex Nan > </td> > </tr> > <tr> > <td width="100">email:</td> > <td> > <a href="mailto:ewchan@ca.ibm.com">ewchan@ca.ibm.com</a><br/> > <a href="mailto:apnan@ca.ibm.com">apnan@ca.ibm.com</a> > </td> > </tr> > <tr> > <td width="100">Last updated:</td> > <td> > <script language="JavaScript" type="text/javascript"> > document.write(document.lastModified); > </script> > </td> > </tr> > </tbody> ></table> ><br/> ><font color="red">Rough workload estimate in person weeks: 4.26PW</font> ><br/> ><table border="1"> > <tbody> > <tr> > <th>Process</th> > <th>Sizing</th> > <th>Names of people doing the work</th> > </tr> > <tr> > <td>Design</td> > <td>3PD</td> > <td rowspan="4">Eugene Chan, Alex Nan</td> > </tr> > <tr> > <td>Code</td> > <td>14PD</td> > </tr> > <tr> > <td>Test</td> > <td>2PD</td> > </tr> > <tr> > <td>Documentation</td> > <td>2PD</td> > </tr> > <tr> > <td>Build and infrastructure</td> > <td>0.3PD</td> > <td>Build team</td> > </tr> > <tr> > <td>Code review & other committer work <br/> > (e.g. check-in, contribution tracking) <br/> > if this is to be contributed by someone who <br/> > is not a committer in the component > </td> > <td>-</td> > <td>N/A - will be done by committer</td> > </tr> > <tr> > <td><b><font color="red">Total</font></b></td> > <td colspan="2"><b><font color="red">Estimate 21.3PD (4.26PW)</font></b></td> > </tr> > </tbody> ></table> ><br> ><h2>Requirement summary</h2> ><p> ><ol> ><li>Provide a way to contribute import and export actions to the Log Navigator context menu. Group actions in cascading menus. <br/> >Third parties should be able to register their own import and export log wizards corresponding to specific import log methods.[1.5 PD] ></li> > <li>Reorganize the Eclipse import and export wizard Profiling and Logging category. Provide two subcategories for import and export logs. [0.5 PD]</li> > <li>Enhance the current communication mechanism between the import log wizard and a custom control to provide host information and enable/disable the import log wizard host selection tab based on the custom control input. [5 PD]</li> > <li>Enhance the log import wizard to support multi host log file elements in custom control. [3 PD]</li> > <li>Enhance the log import wizard framework to support agent-less log import from remote machine, i.e. a remote import that doesnt use the Agent Controller communication framework. The actual import job is done locally but log file is displayed as remote log file under a virtual remote host in Log Navigator. For example the current ftp and http import scenarios fall into this category. [3 PD]</li> > <li>Change both Symptom 0.1 and Symptom 2.0 Import Catalog wizards and capture the source location from where the catalog was imported. Local imports should capture a local file URL and remote imports should capture a URL to the remote host. Also change both Symptom 0.1 and Symptom 2.0 New Catalog wizards to capture the location of the created symptom catalog. [1 PD]</li> ></ol> ></p> ><h2>User interactions</h2> ><p> ><H4>Use case 1: (Requirement 1)</H4> ><ol> > <li>In Log Navigator view, user right-clicks and selects Import > Log File, then he selects which import method he wants to use, the corresponding Import Log File wizard is shown.</li> > <li>User clicks finishes the wizard and the import log job starts.</li> ></ol> ><H4>Use case 2: (Requirement 3, 4, 5)</H4> ><ol> > <li>In Add Log File dialog, user selects a third party log type which resolves log files information of multiple hosts for user automatically. Host tab of Add Log File dialog will be disabled from user selection.</li> > <li>User selects OK to close Add Log File dialog, new log file entries of different hosts are added in log file table, user clicks Finish and import log jobs starts.</li> > <li>Third-party extension will transfer resolved files from remote machines to localhost, and import jobs will import the logs locally and displays them under the hostnames they are transferred from.</li> ></ol> ></p> ><h2>Design summary</h2> ><p> ><ol> > <li>Reorganize the Log Navigator context menu with cascaded group for Import and Export actions. Register the Log Navigator view for external action contribution.</li> > <li>Create new org.eclipse.ui.importWizards categories for Import and Export wizard for log type actions under existing category org.eclipse.tptp.platform.category.trace.import.</li> > <li>Consumers would need to provide host information to each life line in a string having the format lifeline1:host1;lifeline2:host2 and the import log will process the returned custom control input so that each life line maps to its own host. </li> > <li>Add a virtualHost property to the log file element that will be used to create the host model resource in the workspace. The old host property will still be used to distinguish between local log imports and remote imports executed using the Agent Controller. In the import from ftp, http URLs case, the host will be set to local and the virtualHost will be set to the corresponding host found in the URL.</li> > <li>Change the Import Symptom Catalog wizards to set the URL property of the symptom catalog to be the URL of the source file. Change the New Symptom Catalog wizards to set the URL property of the new catalog to a file URL representing the absolute path of the catalog on the local file system.</li> ></ol> ></p> ></body> ></html>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <title>TPTP feature 156527</title> <link rel="stylesheet" type="text/css" href="http://eclipse.org/default_style.css"> </head> <body> <h1>TPTP feature: 156527</h1> <table border="0" cellpadding="2" cellspacing="2"> <tbody> <tr> <td width="100">Author:</td> <td>Eugene Chan <br/> Alex Nan </td> </tr> <tr> <td width="100">email:</td> <td> <a href="mailto:ewchan@ca.ibm.com">ewchan@ca.ibm.com</a><br/> <a href="mailto:apnan@ca.ibm.com">apnan@ca.ibm.com</a> </td> </tr> <tr> <td width="100">Last updated:</td> <td> <script language="JavaScript" type="text/javascript"> document.write(document.lastModified); </script> </td> </tr> </tbody> </table> <br/> <font color="red">Rough workload estimate in person weeks: 4.26PW</font> <br/> <table border="1"> <tbody> <tr> <th>Process</th> <th>Sizing</th> <th>Names of people doing the work</th> </tr> <tr> <td>Design</td> <td>3PD</td> <td rowspan="4">Eugene Chan, Alex Nan</td> </tr> <tr> <td>Code</td> <td>14PD</td> </tr> <tr> <td>Test</td> <td>2PD</td> </tr> <tr> <td>Documentation</td> <td>2PD</td> </tr> <tr> <td>Build and infrastructure</td> <td>0.3PD</td> <td>Build team</td> </tr> <tr> <td>Code review & other committer work <br/> (e.g. check-in, contribution tracking) <br/> if this is to be contributed by someone who <br/> is not a committer in the component </td> <td>-</td> <td>N/A - will be done by committer</td> </tr> <tr> <td><b><font color="red">Total</font></b></td> <td colspan="2"><b><font color="red">Estimate 21.3PD (4.26PW)</font></b></td> </tr> </tbody> </table> <br> <h2>Requirement summary</h2> <p> <ol> <li>Provide a way to contribute import and export actions to the Log Navigator context menu. Group actions in cascading menus. <br/> Third parties should be able to register their own import and export log wizards corresponding to specific import log methods.[1.5 PD] </li> <li>Reorganize the Eclipse import and export wizard Profiling and Logging category. Provide two subcategories for import and export logs. [0.5 PD]</li> <li>Enhance the current communication mechanism between the import log wizard and a custom control to provide host information and enable/disable the import log wizard host selection tab based on the custom control input. [5 PD]</li> <li>Enhance the log import wizard to support multi host log file elements in custom control. [3 PD]</li> <li>Enhance the log import wizard framework to support agent-less log import from remote machine, i.e. a remote import that doesnt use the Agent Controller communication framework. The actual import job is done locally but log file is displayed as remote log file under a virtual remote host in Log Navigator. For example the current ftp and http import scenarios fall into this category. [3 PD]</li> <li>Change both Symptom 0.1 and Symptom 2.0 Import Catalog wizards and capture the source location from where the catalog was imported. Local imports should capture a local file URL and remote imports should capture a URL to the remote host. Also change both Symptom 0.1 and Symptom 2.0 New Catalog wizards to capture the location of the created symptom catalog. [1 PD]</li> </ol> </p> <h2>User interactions</h2> <p> <H4>Use case 1: (Requirement 1)</H4> <ol> <li>In Log Navigator view, user right-clicks and selects Import > Log File, then he selects which import method he wants to use, the corresponding Import Log File wizard is shown.</li> <li>User clicks finishes the wizard and the import log job starts.</li> </ol> <H4>Use case 2: (Requirement 3, 4, 5)</H4> <ol> <li>In Add Log File dialog, user selects a third party log type which resolves log files information of multiple hosts for user automatically. Host tab of Add Log File dialog will be disabled from user selection.</li> <li>User selects OK to close Add Log File dialog, new log file entries of different hosts are added in log file table, user clicks Finish and import log jobs starts.</li> <li>Third-party extension will transfer resolved files from remote machines to localhost, and import jobs will import the logs locally and displays them under the hostnames they are transferred from.</li> </ol> </p> <h2>Design summary</h2> <p> <ol> <li>Reorganize the Log Navigator context menu with cascaded group for Import and Export actions. Register the Log Navigator view for external action contribution.</li> <li>Create new org.eclipse.ui.importWizards categories for Import and Export wizard for log type actions under existing category org.eclipse.tptp.platform.category.trace.import.</li> <li>Consumers would need to provide host information to each life line in a string having the format lifeline1:host1;lifeline2:host2 and the import log will process the returned custom control input so that each life line maps to its own host. </li> <li>Add a virtualHost property to the log file element that will be used to create the host model resource in the workspace. The old host property will still be used to distinguish between local log imports and remote imports executed using the Agent Controller. In the import from ftp, http URLs case, the host will be set to local and the virtualHost will be set to the corresponding host found in the URL.</li> <li>Change the Import Symptom Catalog wizards to set the URL property of the symptom catalog to be the URL of the source file. Change the New Symptom Catalog wizards to set the URL property of the new catalog to a file URL representing the absolute path of the catalog on the local file system.</li> </ol> </p> </body> </html>
View Attachment As Raw
Actions:
View
Attachments on
bug 156527
:
57747
| 58034