Community
Participate
Working Groups
This defect would be used to enable custom event formats (including binary representation). Most of the plumbing is already available some hooks and extended loader support needs to be added. The producer of the custom event format will need to also provide a handler (XMLFragmentHandler) for that format that will be used in the XMLLoader and the plumbing to trigger that handler (explained bellow). We will try to provide a binary format for TPTP profiler traces. Basically the custom format would be translated directly in IXMLLoader (IExtendedLoader) SAX related events (not exactly SAX but very similar) by a custom XMLFragmentHandler which knows how to handle binary data instead of XML text data, the only thing missing is the code that triggers the right XMLFragmentHandler when the format is not XML based. This can be done easily by overriding the XMLLoader.makeScanner() method. The custom (binary) XMLFragmentHandler would need to send SAX related events as it does the binary events processing. An immediate improvement would be to add a set of pair methods in XMLFragmentLoader (I would add a XMLExtendedFragmentLoader interface and update all TPTP know loaders, this will not be a breaking change) which would accept attributeIds (currently I use internally the attribute name hash code, although we could use a different mapping, which can be provided by the agent) and elementIds instead of the String representation, that would avoid the hash code computation. The XMLExtendedFragmentLoader would need to support a mode where a bean with the event data would be passed instead of individual attributes/elements so I will add an addYourselfInContext with a DOM like object as argument, the bean would contain all the data captured in that event, this mode should improve the performance when the data can be quickly converted into a DOM so we don't need to parse it in the loaders. All these changes would enhance and not break the existing infrastructure.
Moved to 4.1 i3, not used in current implementation.
FIx in CVS.
sorry closed the wrong bug
Decrease severity, not critical for 4.1.
Retargeted to 4.2
Need to clean up the spec before implementing this.
Move to 4.2 i4, this being provisional code, currently is not used.
Marked as P2 for further investigation and approval.
Moving to 4.3 as it cannot be contained in 4.2.
Ruth, this is a model defect
This is an important enhancement for TPTP but currently not in scope. It may be part of the soon to be discussed binary event format improvement request.
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 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 originator of this enhancement/defect has an inactive Bugzilla account 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.
