Community
Participate
Working Groups
Generic Recorder Framework improvements. This enhancement covers various Generic Recorder Framework improvements required by recorder implementations (e.g Generic Java API Recorder - see https://bugs.eclipse.org/bugs/show_bug.cgi?id=119688): 1. Support for launching and controlling two or more recorders (separate recording session) or recording agents (single recording session) in parallel. For example, launching and controlling multiple recorders at the same time or launching and controlling multiple recording agents that all record various components of a system on one or more target hosts at the same time. This will require changes to the recording console to handle controlling multiple recording session and recording agents within the same recording session. Also, a method to synchronize (order) recorded events is required. Synchronization may occur at record time (e.g. centralized ticket reservation system) or reliably correlated at post-record time. Preferably, both options would be implemented so the recorder may select the best possible option. 2. Support for launching Java applications for recording without creating/using an Eclipse launch configuration. Often, recorders record Java applications or interaction with a Java application (e.g Generic Java API Recorder - see https://bugs.eclipse.org/bugs/show_bug.cgi?id=119688), to recorder implementations will need a method to launch an internal or external (via the Agent Controller) Java application from the recorder wizard. 3. Support remote recording via the Agent Controller. 4. Provide an extension point for user-defined annotations to a recording session. The extension point would provide: -UI widgets (e.g. button) in the recorder controller view for controlling the user-defined annotation. -Common representation of the user annotations and their data in the trace model. -User-defined implementations of the user-defined annotation invoked on the recorded host (local or remote) when the user invoked the UI widget in the recorder controller view. Provide implementations of the extension point for the following user-defined annotations: -Comment -Start timer (name) -Stop timer (name) -Start transaction (name) -End transaction (name) -Pause recording -Resume recording -Split test (name) -Sync point (name) -Extension point for vendor customizations 5. Support (e.g. model loading) for recorders to emit standard trace model events.
Please assign to Paul.
Reassign to Paul.
Based on improvement #4, the TPTP Trace model and its loaders must leverage an annotation capability (e.g. Trace model instance referencing sections of an external annotation file) to keep large annotation data from exceeding the in-memory model capacity. For more details, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=144950.
Based on improvement #5, recorders should be able to emit custom trace, log and statistical XML fragments which are loaded into their TPTP models (e.g. Trace, Common Base Event and Statistical, respectivly) and references by the resulting recording (e.g. Trace model). For more details, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=139747.
After speaking with the requester of this feature, we have agreed to descope this feature for 4.3. That is, the following will be factored to another feature: 1. Support for launching and controlling two or more recorders (separate recording session) or recording agents (single recording session) in parallel. For example, launching and controlling multiple recorders at the same time or launching and controlling multiple recording agents that all record various components of a system on one or more target hosts at the same time. This will require changes to the recording console to handle controlling multiple recording session and recording agents within the same recording session. Also, a method to synchronize (order) recorded events is required. Synchronization may occur at record time (e.g. centralized ticket reservation system) or reliably correlated at post-record time. Preferably, both options would be implemented so the recorder may select the best possible option. 4. Provide an extension point for user-defined annotations to a recording session. The extension point would provide: UI widgets (e.g. button) in the recorder controller view for controlling the user-defined annotation Common representation of the user annotations and their data in the trace model User-defined implementations of the user-defined annotation invoked on the recorded host (local or remote) when the user invoked the UI widget in the recorder controller view Provide implementations of the extension point for the following user-defined annotations: Comment Start timer (name) Stop timer (name) Start transaction (name) End transaction (name) Pause recording Resume recording Split test (name) Sync point (name) Extension point for vendor customizations The TPTP Trace model and its loaders must leverage an annotation capability (e.g. Trace model instance referencing sections of an external annotation file) to keep large annotation data from exceeding the in-memory model capacity. For more details, see enhancement #144950.
helpwanted for 4.3
Updated the Description Document to better explain the requirements for this enhancement.
*** Bug 140673 has been marked as a duplicate of this bug. ***
Updated Description Document to add https://bugs.eclipse.org/bugs/show_bug.cgi?id=147503.
The AGR recorder can be used as a proof-of-concept (e.g. Eclipse application execution, extensible recorder console, recorder commands, etc.).
Updating version/target based on http://www.eclipse.org/tptp/home/documents/process/development/bugzilla.html.
*** Bug 148236 has been marked as a duplicate of this bug. ***
Updated Description Document based on comment #12.
Updating target to future as requested by the PMC. Enhancements are targeted to future if not in plan for the current release.
Updating sizing.
Approved by the AG.
(In reply to comment #16) For TPTP 4.5.
Requirement removed for 4.5 by the consuming product. Replaced with enhancement https://bugs.eclipse.org/bugs/show_bug.cgi?id=208110.
Consuming product no longer requires this enhancement.
Closing.
